From: Nick Roberts <nickrob@snap.net.nz>
To: Bob Rossi <bob_rossi@cox.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB command "info source"
Date: Wed, 29 Mar 2006 04:21:00 -0000 [thread overview]
Message-ID: <17449.52455.708050.125784@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20060328230121.GG9767@brasko.net>
> > In contrast using MI, GDB does yield this information immediately:
> >
> > nickrob/25 src/gdb/gdb -q -i=mi myprog
> > ~"Using host libthread_db library \"/lib/tls/libthread_db.so.1\".\n"
> > (gdb)
> > -file-list-exec-source-file
> > ^done,line="58",file="myprog.c",fullname="/home/nickrob/myprog.c"
> > (gdb)
>
> Yes, that's because of this line
> mi-cmd-file.c:72 set_default_source_symtab_and_line();
>
> It's a special case for finding the default file. When using annotate 2,
> I do 'info line' followed by 'info source'.
That doesn't seem to work for me:
nickrob/47 src/gdb/gdb -q myprog
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) info line
No line number information available.
(gdb) info source
No current source file.
I do "list main" but that doesn't work for languages lik Ada.
> > Shouldn't "info source" do the same?
> >
> > About -file-list-exec-source-file the manual says:
> >
> > There's no GDB command which directly corresponds to this one.
> >
> > but apart from this difference, they seem pretty similar. Also
> > -file-list-exec-source-files could be likened to "info sources".
> >
> > WDYT?
>
> They are similar but not the same. So I don't know.
The same could be said for -stack-list-frames and backtrace,
-stack-list-locals and "info locals" etc.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2006-03-28 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 22:21 Nick Roberts
2006-03-29 1:23 ` Bob Rossi
2006-03-29 4:21 ` Nick Roberts [this message]
2006-03-29 4:35 ` Bob Rossi
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=17449.52455.708050.125784@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob_rossi@cox.net \
--cc=gdb@sources.redhat.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