From: Daniel Jacobowitz <drow@false.org>
To: Pawel K <pawlaczus@yahoo.com>
Cc: gdb@sourceware.org
Subject: Re: gdb changes the path
Date: Fri, 07 Sep 2007 13:37:00 -0000 [thread overview]
Message-ID: <20070907123531.GA21334@caradoc.them.org> (raw)
In-Reply-To: <227141.71071.qm@web33804.mail.mud.yahoo.com>
On Fri, Sep 07, 2007 at 05:32:01AM -0700, Pawel K wrote:
> --- Daniel Jacobowitz <drow@false.org> wrote:
> > On Fri, Sep 07, 2007 at 02:14:45AM -0700, Pawel K
> > wrote:
> > > 2. How to force gdb to use the relative path as in
> > > breakpoint nr 3 above ?
> >
> > Why? It's a different name for the same file, and
> > GDB knows its full
> > name.
>
> Since when I specify the breakpoint like:
> (gdb) bre functions.h:100
>
> I cannot "list" the source lines.
You may want to try a GDB 6.7 snapshot. I hope this has been
improved.
> Do You have any idea what can be wrong ?
No, sorry.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-09-07 12:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 9:21 Pawel K
2007-09-07 11:49 ` Daniel Jacobowitz
2007-09-07 12:35 ` Pawel K
2007-09-07 13:37 ` Daniel Jacobowitz [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=20070907123531.GA21334@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pawlaczus@yahoo.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