https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997
Liu Qiang changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997
--- Comment #5 from Liu Qiang ---
Should I try to enable the MD_FALLBACK_FRAME_STATE_FOR for target specific
fallback mechanism?
in file src/gcc-5.3.0/libgcc/config/i386/linux-unwind.h,
#ifndef inhibit_libc
#define MD_FALLBACK_FRAME_STATE_FOR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997
--- Comment #4 from Liu Qiang ---
Hello everybody.
I build the powerpc64 crosstoolchain with removing the
'gcc_assert(code==URC_NO_REASON)', and run the new system built by it. The
program (python3 with thread exiting) terminated by SIGSEGV ins
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997
--- Comment #3 from Liu Qiang ---
Latest info:
uw_frmae_state_for return: 5
_URC_END_OF_STACK = 5,
And I find that it is harmless to remove the gcc_assert(...).
will it be the resolution?
uw_init_context_1 (struct _Unwind_Context *context,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997
--- Comment #2 from Liu Qiang ---
yeah, i recommitted the page before the first committing done.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997
Liu Qiang changed:
What|Removed |Added
Keywords||EH
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997
Andreas Schwab changed:
What|Removed |Added
Severity|blocker |normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997
--- Comment #1 from Andreas Schwab ---
*** Bug 69998 has been marked as a duplicate of this bug. ***
