From: Andrew Cagney <cagney@gnu.org>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: Monika Chaddha <monika@acmet.com>, gdb@sources.redhat.com
Subject: Re: List command question
Date: Wed, 19 May 2004 14:22:00 -0000 [thread overview]
Message-ID: <40AB6D86.4090409@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0405181707100.30853@lazy>
> I get no line number known for main...
>
> manjo@nefertiti:~/tests> gdb64 hellow1
> GNU gdb 6.1
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for
> details.
> This GDB was configured as "ppc64-suse-linux"...Using host libthread_db
> library "/lib64/tls/libthread_db.so.1".
>
> (gdb) list
> 1 ../sysdeps/powerpc/powerpc64/elf/start.S: No such file or
> directory.
> in ../sysdeps/powerpc/powerpc64/elf/start.S
> (gdb) list main
> No line number known for main.
> (gdb)
GDB has the concept of a current source-and-line (SAL). When GDB starts
it initializes it to something. Looking at the behavior you've
illustrated, it tries in order: main's SAL; entry-point's SAL; ???
I guess the question is, should GDB set SAL to main when main doesn't
have any line number information?
Note here that this will end up interacting with the ``start'' mechanism
that Joel is playing with - its a mechanism for doing run-to ``main''.
So this will be a language dependent concept.
Andrew
prev parent reply other threads:[~2004-05-19 14:22 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
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 [this message]
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=40AB6D86.4090409@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=manjo@austin.ibm.com \
--cc=monika@acmet.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