Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: MI: full file name
Date: Mon, 21 Nov 2005 15:07:00 -0000	[thread overview]
Message-ID: <20051121150732.GA20963@nevyn.them.org> (raw)
In-Reply-To: <20051121145453.GC14604@white>

On Mon, Nov 21, 2005 at 09:54:53AM -0500, Bob Rossi wrote:
> On Mon, Nov 21, 2005 at 05:53:06PM +0300, Vladimir Prus wrote:
> > On Monday 21 November 2005 17:45, Bob Rossi wrote:
> > > > 1. Can I get full file name in MI output somehow?
> > >
> > > -file-list-exec-source-file
> > 
> > Thanks. 
> > 
> > Is there any reason why I need separate MI command? Can't "*stopped" packet 
> > include full file name as well?
> 
> I believe this is in the works. Actually, this might already work with
> mi2 or latest CVS. Maybe someone else knows better. I've been very busy,
> and haven't had time to keep up.

Looks like it's been done in 6.4:

drow@caradoc:~% gdb -i=mi ~/nevyn-home/debugging/printf 
~"GNU gdb 6.3.90_20051119-debian\n"
~"Copyright 2004 Free Software Foundation, Inc.\n"
~"GDB is free software, covered by the GNU General Public License, and you are\n"
~"welcome to change it and/or distribute copies of it under certain conditions.\n"
~"Type \"show copying\" to see the conditions.\n"
~"There is absolutely no warranty for GDB.  Type \"show warranty\" for details.\n"
~"This GDB was configured as \"x86_64-linux-gnu\"..."
~"Using host libthread_db library \"/lib/libthread_db.so.1\".\n"
~"\n"
(gdb) 
-break-insert main
^done,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x08048394",func="main",file="debugging/printf.c",line="6",times="0"}
(gdb) 
-exec-run
^running
(gdb) 
&"warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4\n"
*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x08048394",func="main",args=[{name="argc",value="1"},{name="argv",value="0xffffc4b4"}],file="debugging/printf.c",line="6"}
(gdb) 

And then again with appropriate "dir" so GDB can find the file:

-exec-run
^running
(gdb) 
&"warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4\n"
*stopped,reason="breakpoint-hit",bkptno="1",thread-id="0",frame={addr="0x08048394",func="main",args=[{name="argc",value="1"},{name="argv",value="0xffffc974"}],file="debugging/printf.c",fullname="/home/drow/mnt/nevyn/home/drow/debugging/printf.c",line="6"}
(gdb) 

I didn't try 6.3.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-11-21 15:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 14:44 Vladimir Prus
2005-11-21 14:46 ` Bob Rossi
2005-11-21 14:53   ` Vladimir Prus
2005-11-21 14:55     ` Bob Rossi
2005-11-21 15:07       ` Daniel Jacobowitz [this message]
2005-11-22  8:01         ` Anon CVS (Was: MI: full file name) Vladimir Prus
2005-11-22 12:10           ` Bob Rossi
2005-11-22 12:19             ` Vladimir Prus
2005-11-22 12:47               ` Andreas Schwab
2005-11-23 13:53   ` MI: full file name Vladimir Prus
2005-11-23 14:53     ` Daniel Jacobowitz
     [not found]     ` <7f89a3ea0512221820u4512e691x59d20442123d3086@mail.gmail.com>
2005-12-23  7:09       ` Vladimir Prus

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=20051121150732.GA20963@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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