Hi
Thanks for the heads up. The coincidence is funny -- a file that hasn't
been touched for years.
I do believe that we need the logic around the `first` flag for
consistency with the other unwind-*.c implementations. This can be
verified by running the tests in the included libbacktrace library (e.g.
via make check), in particular btest.c . See
https://github.com/ianlancetaylor/libbacktrace/issues/43 for the
downstream ticket.
Best regards
Kirill
On 08.09.20 14:08, Martin Storsjö wrote:
Hi,
On Mon, 7 Sep 2020, Kirill Müller via Gcc-patches wrote:
As requested, attaching a patch for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96948. This solves a
problem with _Unwind_Backtrace() on mingw64 + SEH.
What a coincidence - I actually sent a patch for the exact same thing
last week, see
https://gcc.gnu.org/pipermail/gcc-patches/2020-September/553082.html.
My version doesn't set gcc_context.cfa though, but is simpler by
avoiding the whole "first" flag logic.
I can send an updated patch that also sets gcc_context.cfa in a smilar
manner to the previous one.
// Martin
