Closed Cl00e9ment closed 3 years ago
Hi @Cl00e9ment,
Could you confirm which version of bugsnag-go you are using? Thanks
I'm using the latest version (2.1.1) which uses panicwrap 1.3.2. The bug I'm refering to has been fixed in panicwrap 1.3.3 (see changelog https://github.com/bugsnag/panicwrap/releases/tag/v1.3.3), so it would be great if the panicwrap version was bumped to the latest one (1.3.4).
Hi @Cl00e9ment,
Thanks for confirming, yes we will look to update that as soon as priorities allow.
Hey @Cl00e9ment, bumped the panicwrap
version to v1.3.4 in bugsnag-go
v2.1.2. Thanks for raising this issue!
Please bump panicwrap version to fix the issue. See https://github.com/bugsnag/panicwrap/issues/20 Thanks