From: Robert Lipe <robertl@dgii.com>
To: law@cygnus.com
Cc: acs@acm.org, egcs@cygnus.com, gcc2@cygnus.com,
Ronald Joe Record <rr@sco.com>
Subject: Re: egcs 10-31 and UnixWare
Date: Sun, 09 Nov 1997 11:16:00 -0000 [thread overview]
Message-ID: <19971109131009.64698@dgii.com> (raw)
In-Reply-To: <1894.879094444@hurl.cygnus.com>
Given the similarity in the symptoms and the environments, I
suspect that the Unixware and OpenServer problems are related.
I don't know why he's getting nailed with it on every executable
and I'm only getting hammered in one test case, though.
> > Here's the backtrace:
> > #0 0xbffb3783 in kill ()
> > #1 0xbffe3528 in abort ()
> > #2 0x804853e in __do_global_dtors_aux ()
> > #3 0x8048ffd in _fini ()
> Can you do something like
>
> x/50i __do_global_dtors_aux
>
>
> Basically I don't see how the __do_global_dtors_aux routine from gcc's
> crtstuff.c can call abort -- unless abort is on the dtor list. So I'm
> wondering if you're getting the correct crtbegin.o file.
Abort isn't on the dtor list in my case, but I"m starting to
really distrust GDB here. According to a print __DTOR_LIST__[1],
I don't have a dtor list, clearly there are destructors running.
> Or maybe gdb is lying and you called abort from __deregister_frame which
> would indicate that the exception handlers never got registered in the
> first place or were clobbered.
What if exit() is recursing?
$ gdb a.out
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.14-95q4 (i486-unknown-sco3.2v5.0.0elf),
Copyright 1995 Free Software Foundation, Inc...
Breakpoint 1 at 0x80484b8
(gdb) break exit
Breakpoint 2 at 0x8048498
(gdb) break __do_global_dtors_aux
Breakpoint 3 at 0x80485a6
(gdb) break __deregister_frame
Breakpoint 4 at 0x8048e24
(gdb) run
Starting program: /home/play/ss/a.out
Breakpoint 1 at 0x8003ded9
Breakpoint 2 at 0x800196c4
++count
++count
Base
--count
Breakpoint 2, 0x800196c4 in exit ()
(gdb) cont
Continuing.
Breakpoint 3, 0x80485a6 in __do_global_dtors_aux ()
(gdb) cont
Continuing.
--count
--count
Breakpoint 2, 0x800196c4 in exit ()
(gdb) cont
Continuing.
Breakpoint 1, 0x8003ded9 in abort ()
(gdb)
This can't be good.
Hmmm. Sure enough. If I change the "exit 0" in the p9732b
program I'd just sent to "_exit 0", it works even with the
HAVE_ATEXIT.
> Can you compile frame.c with debug symbols, add it to libgcc, then put
> a breakpoint in __deregister_frame to see what's going on?
My breakpoint on __deregister_frame never gets called.
RJL
next prev parent reply other threads:[~1997-11-09 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-07 9:25 acs
1997-11-09 10:14 ` Jeffrey A Law
1997-11-09 11:16 ` Robert Lipe [this message]
1997-11-09 13:49 ` Jeffrey A Law
1997-11-09 12:35 ` acs
1997-11-09 13:00 ` Robert Lipe
1997-11-09 17:00 ` Jeffrey A Law
1997-11-09 18:35 ` Joe Buck
1997-11-09 21:08 ` Joern Rennecke
1997-11-09 20:32 ` Robert Lipe
1997-11-10 14:57 ` H.J. Lu
1997-11-10 14:57 ` Robert Lipe
1997-11-10 12:27 ` 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=19971109131009.64698@dgii.com \
--to=robertl@dgii.com \
--cc=acs@acm.org \
--cc=egcs@cygnus.com \
--cc=gcc2@cygnus.com \
--cc=law@cygnus.com \
--cc=rr@sco.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).