Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: example fix to pr 2360
Date: Thu, 20 Dec 2007 20:23:00 -0000	[thread overview]
Message-ID: <20071220194945.GA28256@caradoc.them.org> (raw)
In-Reply-To: <e394668d0712201137i21a4f148n3a9dcdad5dae5e6d@mail.gmail.com>

On Thu, Dec 20, 2007 at 11:37:13AM -0800, Doug Evans wrote:
> On Dec 16, 2007 4:01 PM, Daniel Jacobowitz <drow@false.org> wrote:
> > Are there any examples of this without #line?
> 
> Thanks for the review.  I'm not aware of any examples without #line.
> 
> While dwarf doesn't understand inodes the paths do have some canonical
> behaviour.  e.g. As I understand it, posix says //tmp/foo == /tmp/foo.
>  I recognize the paths are from the compilation host not the debug
> host, we could write a path canonicalizer.

Actually, I believe this is one of the few places where / and // are
separate, and POSIX allows //tmp to be different from /tmp.  /tmp//foo
is another story.

> But no matter, I can certainly pursue a different fix for the problem
> at hand, perhaps by adding an option to gcc to set DW_AT_comp_dir.

Does -fworking-directory help?  That's the default if you preprocess
with -g, if I understand correctly.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-12-20 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 23:55 Douglas Evans
2007-11-27  0:11 ` Douglas Evans
2007-12-17  0:44 ` Daniel Jacobowitz
2007-12-20 19:40   ` Doug Evans
2007-12-20 20:23     ` 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=20071220194945.GA28256@caradoc.them.org \
    --to=drow@false.org \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /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