From: Elena Zannoni <ezannoni@redhat.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] new test for separate debug info
Date: Thu, 13 Nov 2003 19:23:00 -0000 [thread overview]
Message-ID: <16307.55884.842479.274705@localhost.redhat.com> (raw)
In-Reply-To: <20031113175555.9EE3F4B3FA@berman.michael-chastain.com>
Michael Elizabeth Chastain writes:
> My test bed says:
>
> binutils HEAD, stabs+
> 3 ERROR, 7 PASS, 44 FAIL, 1 UNRESOLVED
> # not okay
woah. I didn't test this. And I guess nobody did until now. RH ships
only dwarf2 toolchains.
>
> The results are the same for all versions of gcc tested.
>
> Here is an excerpt from gdb.log:
>
> # gdb HEAD, gcc 3.3.2, binutils HEAD, -gstabs+
> (gdb) dir /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base
> Source directories searched: /berman/fsf/_today_/source/gdb/HEAD/src/gdb/testsuite/gdb.base:$cdir:$cwd
> (gdb) file /berman/fsf/_today_/berman/test/gdb.base/sepdebug
> Reading symbols from /berman/fsf/_today_/berman/test/gdb.base/sepdebug...Reading symbols from /berman/fsf/_today_/berman/test/gdb.base/.debug/sepdebug.debug...Can't find any code sections in symbol file
> (gdb) ERROR: couldn't load /berman/fsf/_today_/berman/test/gdb.base/sepdebug into gdb.
> delete breakpoints
> (gdb) UNRESOLVED: gdb.base/sepdebug.exp: Delete all breakpoints when none
> From gdb-patches-return-28583-mec.gnu=mindspring.com@sources.redhat.com Wed Nov 12 17:26:42 2003
>
> It looks like either binutils or gdb needs some work.
>
the warning is coming from gdb, dbxread.c. I'll look into this.
> If you could kludge the test to handle "Can't find any code sections
> in symbol file" then I would be happy with the test script as a test
> script.
>
OK.
elena
next prev parent reply other threads:[~2003-11-13 19:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 17:55 Michael Elizabeth Chastain
2003-11-13 19:23 ` Elena Zannoni [this message]
2003-11-13 20:08 ` Elena Zannoni
2003-11-13 23:15 ` Elena Zannoni
2003-11-14 4:22 ` Daniel Jacobowitz
2003-11-14 14:34 ` Elena Zannoni
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 2:47 Michael Elizabeth Chastain
2004-01-14 15:09 ` Elena Zannoni
2004-01-13 22:24 Michael Elizabeth Chastain
2004-01-13 23:37 ` Elena Zannoni
2004-01-13 5:19 Michael Elizabeth Chastain
2004-01-13 17:18 ` Elena Zannoni
2004-01-13 2:28 Michael Elizabeth Chastain
2004-01-13 4:49 ` Elena Zannoni
2003-11-14 19:37 Michael Elizabeth Chastain
2003-11-14 20:09 ` Elena Zannoni
2004-01-12 17:20 ` Elena Zannoni
2004-01-12 22:01 ` Andrew Cagney
2004-01-12 22:28 ` Daniel Jacobowitz
2004-01-12 23:11 ` Elena Zannoni
2004-01-12 23:20 ` Daniel Jacobowitz
2004-01-13 3:12 ` Ian Lance Taylor
2004-01-16 19:55 ` Andrew Cagney
2004-01-16 22:41 ` Daniel Jacobowitz
2003-11-14 15:18 Michael Elizabeth Chastain
2003-11-14 15:52 ` Elena Zannoni
2003-11-14 5:14 Michael Elizabeth Chastain
2003-11-14 14:30 ` Elena Zannoni
2003-11-14 4:57 Michael Elizabeth Chastain
2003-11-14 14:32 ` Elena Zannoni
2003-11-13 16:49 Michael Elizabeth Chastain
2003-11-12 22:13 Elena Zannoni
2003-11-12 22:29 ` Daniel Jacobowitz
2003-11-13 16:18 ` 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=16307.55884.842479.274705@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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