From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, jkj@sco.com, mec.gnu@mindspring.com
Cc: ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com
Subject: Re: Phasing out Dwarf 1?
Date: Thu, 06 May 2004 15:00:00 -0000 [thread overview]
Message-ID: <20040506150021.8175C4B104@berman.michael-chastain.com> (raw)
For gdb 6.1, I get some noise, but the backtrace looks okay:
(top-gdb) backtrace
#0 captured_main (data=0xbffff690) at /tmp/chastain/d1/gdb-6.1/gdb/main.c:117
During symbol reading, DIE @ 0x1df "interpreter_p", type modifier 'const' ignored.
During symbol reading, DIE @ 0x1d25 "", array subscript format 0x1 not handled yet.
During symbol reading, DIE @ 0x14d7d "pthread_spinlock_t", type modifier 'volatile' ignored.
#1 0x08080321 in do_catch_errors (uiout=0x82b72a0, data=0xbffff648)
at /tmp/chastain/d1/gdb-6.1/gdb/top.c:523
#2 0x08080124 in catcher (func=0x8080305 <do_catch_errors>,
func_uiout=0x82b72a0, func_args=0xbffff648, func_val=0xbffff654,
func_caught=0xbffff650, errstring=0x822a7c8 "", gdberrmsg=0x0, mask=6)
at /tmp/chastain/d1/gdb-6.1/gdb/top.c:430
#3 0x0808035c in catch_errors (func=0x807aa66 <captured_main>,
func_args=0xbffff690, errstring=0x822a7c8 "", mask=6)
at /tmp/chastain/d1/gdb-6.1/gdb/top.c:535
#4 0x0807b87a in gdb_main (args=0xbffff690)
at /tmp/chastain/d1/gdb-6.1/gdb/main.c:814
#5 0x0807aa21 in main (argc=1, argv=0xbffff734)
at /tmp/chastain/d1/gdb-6.1/gdb/gdb.c:35
This is on a native i686-pc-linux-gnu, red hat enterprise linux 3,
gdb compiled with gcc 3.2.3-24-rh. "make CFLAGS=-gdwarf"
I get similar three messages "During symbol reading ..." with gdb 6.0
operating on gdb 6.0, and also gdb 5.3 operating on gdb 5.3.
> What are the results if the testsuite is run?
I already posted this link from February 2003:
http://sources.redhat.com/ml/gdb-patches/2003-02/msg00293.html
I will do it again with gdb 6.1 but it will take some time.
> Or to look at it another way, when was the last time (other than SCO's
> 5.1) that anyone saw a working dwarf-1 GDB?
It looks like gdb is working, with some glitches, and the test suite
has been busted for a while.
Michael C
next reply other threads:[~2004-05-06 15:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 15:00 Michael Elizabeth Chastain [this message]
2004-05-07 1:19 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-05-05 22:01 Michael Elizabeth Chastain
2004-05-06 14:02 ` Andrew Cagney
2004-05-06 20:11 ` Mark Kettenis
2004-05-05 21:33 Michael Elizabeth Chastain
2004-05-05 5:24 Michael Elizabeth Chastain
2004-05-05 14:31 ` Andrew Cagney
2004-05-05 16:05 ` Kean Johnston
2004-05-05 18:30 ` Stan Shebs
2004-05-05 18:53 ` Kean Johnston
2004-05-05 5:03 Michael Elizabeth Chastain
2004-05-03 15:56 Michael Elizabeth Chastain
2004-05-04 15:37 ` Andrew Cagney
2004-05-04 17:09 ` Nathan J. Williams
2004-05-04 17:19 ` Kean Johnston
2004-05-05 0:28 ` Stan Shebs
2004-05-05 5:57 ` Jim Blandy
2004-05-10 21:09 ` Andrew Cagney
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=20040506150021.8175C4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=jkj@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