Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ramana Radhakrishnan" <ramana.radhakrishnan@codito.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: "Andreas Schwab" <schwab@suse.de>,
	manjo@austin.ibm.com, gdb@sources.redhat.com
Subject: Re: List command question
Date: Sat, 15 May 2004 18:07:00 -0000	[thread overview]
Message-ID: <1109.203.145.159.41.1084645193.squirrel@203.145.159.41> (raw)
In-Reply-To: <2914-Sat15May2004113549+0300-eliz@gnu.org>


Thus spake Eli Zaretskii
>> 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?

Is it possible that bis start.S is alone compiled with debug info in such
a case  ? Would that be a valid enough reason for this to happen  ? But
isnt it strange that it can find just one file even if libc was compiled
with debug info ?




cheers
Ramana


>


----
Ramana Radhakrishnan
Codito Technologies


  parent reply	other threads:[~2004-05-15 18:07 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
2004-05-15 18:07     ` Ramana Radhakrishnan [this message]
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=1109.203.145.159.41.1084645193.squirrel@203.145.159.41 \
    --to=ramana.radhakrishnan@codito.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=manjo@austin.ibm.com \
    --cc=schwab@suse.de \
    /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