From: Andrew Cagney <cagney@gnu.org>
To: Olivier Crete <tester@tester.ca>
Cc: gdb@sources.redhat.com
Subject: Re: Wierd problem with gdb 6.x and separate debug info
Date: Sat, 01 May 2004 14:11:00 -0000 [thread overview]
Message-ID: <4093B02A.5040506@gnu.org> (raw)
In-Reply-To: <1083417821.8129.31.camel@TesterTop.tester.ca>
> Hi,
>
> On Sat, 2004-05-01 at 15:00, Andrew Cagney wrote:
>
>>> Look at, and run, the gdb.base/sepdebug.exp testcase. Running that will
>>> at least confirm that the mechanism is working.
>
>
> I get 2 errors.
> FAIL: run until function breakpoint
> FAIL: run until function breakpoint, optimized file
On Red Hat's RHEL 3 system (i386) I see no failures.
Do you get the other warnings (see gdb.log)? If not, then these
failures are probably due to other bugs.
> Both using yesterday's cvs snapshot and 6.0.
>
>
>>> After that, it depends on the system, look at "set
>>> debug-file-directory". Your system's debug directory may not match GDBs.
>
>
> I've put the debug info in .debug/ in the same directory as the libs..
Ok, I guess it is finding the relevant files. Look in gdb.log and check
exactly how objcopy is run.
Andrew
next prev parent reply other threads:[~2004-05-01 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 8:39 Olivier Crete
2004-05-01 13:00 ` Andrew Cagney
2004-05-01 13:23 ` Olivier Crete
2004-05-01 14:11 ` Andrew Cagney [this message]
2004-05-01 19:14 ` Olivier Crete
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=4093B02A.5040506@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=tester@tester.ca \
/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