From: Andreas Schwab <schwab@suse.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: manjo@austin.ibm.com, gdb@sources.redhat.com
Subject: Re: List command question
Date: Sat, 15 May 2004 13:16:00 -0000 [thread overview]
Message-ID: <je4qqhzv7s.fsf@sykes.suse.de> (raw)
In-Reply-To: <2914-Sat15May2004113549+0300-eliz@gnu.org> (Eli Zaretskii's message of "Sat, 15 May 2004 11:35:50 +0200")
"Eli Zaretskii" <eliz@gnu.org> writes:
>> From: Andreas Schwab <schwab@suse.de>
>> Date: Fri, 14 May 2004 21:27:18 +0200
>>
>> You can't expect meaningful results without debugging information as
>> nothing else is providing information about source files.
>
> I tried this with GDB 6.1 and the DJGPP toolchain, and GDB said "(no
> debugging symbols found)", which is reasonable, IMHO.
>
> Why didn't it do so in Manoj's case?
Because there is _some_ debugging info, presumably from libc. And once
gdb has found any debugging info at all it will not say "(no debugging
symbols found)" any more, even if more objects without debugging info are
crossed.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-05-15 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 18:29 Manoj Iyer
2004-05-14 19:27 ` Andreas Schwab
2004-05-15 8:37 ` Eli Zaretskii
2004-05-15 13:16 ` Andreas Schwab [this message]
2004-05-15 18:07 ` Ramana Radhakrishnan
2004-05-15 7:40 ` Monika Chaddha
2004-05-17 15:29 ` Manoj Iyer
2004-05-17 18:35 ` Andrew Cagney
2004-05-19 2:24 ` Manoj Iyer
2004-05-19 14:22 ` 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=je4qqhzv7s.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.ibm.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