From: Thomas Weise <tom@zaphod.wh9.tu-dresden.de>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: DWARF EH problem (was: Re: (971023) Addendum: i386-linux-gnulibc1 g++ test results)
Date: Sat, 15 Nov 1997 04:58:00 -0000 [thread overview]
Message-ID: <346DAA6B.4762@zaphod.wh9.tu-dresden.de> (raw)
In-Reply-To: <15769.878525581@hurl.cygnus.com>
Jeffrey A Law wrote:
>
> In message < 345CE1AD.36A6@mail.wh9.tu-dresden.de >you write:
> > I've got a similiar problem, but unfortunately I'm not able to narrow it
> > to an appropriate test case yet. (Linux 2.0.29/libc5.4.39). The symptom
> > is after throwing an exception my process hangs for a time, and after
> > that it crashes with SIGSEGV. This may depend on the produced binary, as
> > I've seen it working by varying static libraries needed. (Those libs
> > have been compiled with exactly the same options). However, *all works
> > fine* rebuilding completely using -fsjlj-exceptions, what confirms that
> > this bug apears in snapshots later then egcs-2.90.06 when DWARF EH has
> > been put in.
> >
> > As there should be some EH patches in next snapshot I hope they will
> > solve this problem as well. I would also greatly appreciate some hints
> > on how to provide a helpful bug report for cases like this.
> I don't think the EH fixes for the next snapshot fix _all_ of these
> kinds of problems -- in fact, I've got at least one testcase that
> still behaves in a similar fashion.
From egcs-971105 to 971114 the symptom has changed in so far as the
process does not hang for a time any more after throwing an exception,
but it crashes immediately. However, I still cannot narrow it to a
testcase.
Tom.
--
Thomas Weise, http://www.inf.tu-dresden.de/~tw4
Dresden University of Technology, Department of Computer Science
next prev parent reply other threads:[~1997-11-15 4:58 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-23 20:19 (971023) i386-linux-gnulibc1 gcc/g++ test results Mumit Khan
1997-10-23 21:30 ` (971023) Addendum: i386-linux-gnulibc1 g++ " Mumit Khan
1997-10-23 23:12 ` H.J. Lu
1997-10-24 1:43 ` Theodore Papadopoulo
1997-11-01 21:53 ` Jeffrey A Law
1997-11-02 10:26 ` Thomas Weise
1997-11-02 10:30 ` Thomas Weise
1997-11-02 19:06 ` Jeffrey A Law
1997-11-15 4:58 ` Thomas Weise [this message]
[not found] ` <199710240843.KAA07400.cygnus.egcs@mururoa.inria.fr>
1997-10-24 9:35 ` Jason Merrill
1997-10-24 10:46 ` Robert Lipe
1997-10-24 10:59 ` Mumit Khan
1997-10-24 12:11 ` EH bug in Makefile.in H.J. Lu
1997-10-24 14:30 ` Mumit Khan
1997-10-24 14:35 ` H.J. Lu
1997-10-25 9:49 ` Mumit Khan
1997-10-25 20:34 ` Joe Buck
1997-10-26 0:56 ` Mumit Khan
1997-10-26 16:30 ` [ECGS] " chip
[not found] ` <9710260755.AA26107.cygnus.egcs@modi.xraylith.wisc.edu>
1997-10-26 1:17 ` Jason Merrill
1997-10-26 9:49 ` Jeffrey A Law
1997-10-25 11:19 ` acs
1997-10-25 12:18 ` H.J. Lu
1997-10-24 16:16 ` Robert Lipe
1997-10-26 10:22 ` Jeffrey A Law
1997-10-26 12:39 ` EH in egcs H.J. Lu
1997-10-26 12:39 ` Jason Merrill
1997-10-26 16:21 ` H.J. Lu
1997-10-26 19:34 ` Alexandre Oliva
1997-10-26 19:34 ` H.J. Lu
1997-10-26 18:21 ` Alexandre Oliva
1997-10-26 20:44 ` Oleg Krivosheev
1997-10-27 10:50 ` SGI STL patch Oleg Krivosheev
1997-10-27 11:57 ` Joe Buck
1997-10-27 12:00 ` Jason Merrill
1997-10-27 16:30 ` Matt Austern
1997-10-28 15:42 ` Oleg Krivosheev
1997-10-28 17:57 ` Matt Austern
1997-10-28 15:58 ` Oleg Krivosheev
1997-10-28 17:57 ` Matt Austern
1997-10-27 12:24 ` Alexander Stepanov
1997-10-23 22:55 ` (971023) i386-linux-gnulibc1 gcc/g++ test results H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=346DAA6B.4762@zaphod.wh9.tu-dresden.de \
--to=tom@zaphod.wh9.tu-dresden.de \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).