Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
Subject: Re: Filename with "./" in breakpoint command
Date: Sat, 03 Dec 2005 15:01:00 -0000	[thread overview]
Message-ID: <20051203150037.GD10592@white> (raw)
In-Reply-To: <u3blas01t.fsf@gnu.org>

On Sat, Dec 03, 2005 at 04:54:54PM +0200, Eli Zaretskii wrote:
> > Date: Sat, 3 Dec 2005 09:21:49 -0500
> > From: Bob Rossi <bob@brasko.net>
> > Cc: Vladimir Prus <ghost@cs.msu.su>, gdb@sources.redhat.com
> > 
> > > What are the actual source file names recorded in the debug info?
> > > Please show us that, and we will be able to reason whether this is a
> > > feature, a bug, or a missing feature.
> > 
> > Eli, I can reproduce this like this,
> >   tmp/
> >     one/
> >       uut.c uut.h
> >     two/
> >       uut.c uut.h main.c
> > 
> > If I compile each file in there own directory with -g and then link in
> > directory two/ and then start GDB from there, the command
> >   b uut.c:5 works for me and b ./uut.c:5 doesn't. If I compile 
> > gcc -S uut.c in either directory, the assembly file says the name is
> > "uut.c". Is there a better way to tell you what the debug info says?
> 
> Yes, there is a better way: type "info sources" inside GDB.

O, of course:

(gdb) info sources
/home/bob/tmp/tmp/tmp/tmp/one/uut.c,
/home/bob/tmp/tmp/tmp/tmp/two/uut.c, 
/home/bob/tmp/tmp/tmp/tmp/two/main.c


-file-list-exec-source-files
^done,files=[{file="uut.c",fullname="/home/bob/tmp/tmp/tmp/tmp/one/uut.c"},
             {file="uut.c",fullname="/home/bob/tmp/tmp/tmp/tmp/two/uut.c"},
             {file="main.c",fullname="/home/bob/tmp/tmp/tmp/tmp/two/main.c"}]

Bob Rossi


  reply	other threads:[~2005-12-03 15:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-03 12:58 Vladimir Prus
2005-12-03 14:17 ` Eli Zaretskii
2005-12-03 14:22   ` Bob Rossi
2005-12-03 14:55     ` Eli Zaretskii
2005-12-03 15:01       ` Bob Rossi [this message]
2005-12-05  6:53   ` Vladimir Prus
2005-12-05 18:39     ` Eli Zaretskii
2005-12-05 18:56       ` Daniel Jacobowitz
2005-12-06  4:27         ` Eli Zaretskii
2005-12-06  4:55           ` Daniel Jacobowitz
2005-12-06 11:56             ` Bob Rossi
2005-12-06 14:01               ` Joel Brobecker
2005-12-06 14:26                 ` Andrew STUBBS
2005-12-06 20:13               ` Eli Zaretskii
2005-12-06 20:11             ` Eli Zaretskii
2005-12-06 20:17               ` Daniel Jacobowitz
2005-12-06 21:02                 ` Eli Zaretskii
2005-12-06 21:09                   ` Daniel Jacobowitz
2005-12-06 22:32                     ` Eli Zaretskii
2005-12-07  7:49                     ` Vladimir Prus
2005-12-07 14:51                       ` Daniel Jacobowitz
2005-12-07 16:46                         ` Vladimir Prus
2005-12-08 20:53                           ` Paul Gilliam
2005-12-03 14:19 ` 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=20051203150037.GD10592@white \
    --to=bob@brasko.net \
    --cc=eliz@gnu.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