This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Crashes inside libgcc_s_dw2-1.dll
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Kai Tietz <ktietz70 at googlemail dot com>
- Cc: iant at google dot com, gcc at gcc dot gnu dot org
- Date: Tue, 21 May 2013 21:23:18 +0300
- Subject: Re: Crashes inside libgcc_s_dw2-1.dll
- References: <83obc6x4fh dot fsf at gnu dot org> <CAKOQZ8zJNiJ+d+GM-kiaXKDEKnTEGJKX1T860pvGVBgHEEeYWQ at mail dot gmail dot com> <83d2smwc2m dot fsf at gnu dot org> <CAEwic4ZaQv1mJ1ZKP06f2F4RaB9kpdb5ah_FHi5-Qh=dzBvR5Q at mail dot gmail dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Mon, 20 May 2013 12:18:29 +0200
> From: Kai Tietz <ktietz70@googlemail.com>
> Cc: Ian Lance Taylor <iant@google.com>, gcc Mailing List <gcc@gcc.gnu.org>
>
> The issue is there that after an unload of libgcc on pe-coff, the
> function __decregister_frame_info_bases might be not called.
That's probably true (assuming that cygming-crtbegin.c decided at
startup time that libgcc DLL is loaded). But this cannot be the whole
story, because the call to 'abort' happens before libgcc is unloaded
at program exit time. See my other message I just sent in this
thread. If I set a breakpoint on __decregister_frame_info_bases, I
see that it calls 'abort' the very first time it is called, when
libgcc is still very much loaded into the process.
Thanks.