Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] new substitute path when loading feature
Date: Tue, 13 May 2008 21:18:00 -0000	[thread overview]
Message-ID: <4829E7DA.3010606@qnx.com> (raw)
In-Reply-To: <20080513190818.GA13776@caradoc.them.org>

Daniel Jacobowitz wrote:
> On Tue, May 13, 2008 at 02:55:41PM -0400, Aleksandar Ristovski wrote:
>> Now without my change, this will sometimes work, sometimes it won't. For example, if the program was compiled on windows like this:
>>
>> C:\Temp\dirs\debug>gcc -g -O0 -c ../main.c -o main.o
>>
>> things would work. However if built like this:
>>
>> C:\Temp\dirs\debug>gcc -g -O0 -c c:\Temp\dirs\main.c -o main.o
>>
>> things would not work (as shown above). 
> 
> Is this just because of the slashes?  I have a patch which makes
> Unix-configured GDB more tolerant of DOS paths and drive names.  I
> can post it if you like; I've been meaning to.

No, this particular issue is not because of the slashes, but rather due to IS_ABSOLUTE_PATH returning false on a path like "c:/Temp...".

> 
>> In any case, it seems right to be able to rewrite paths at readin and let 
>> gdb "see" the binaries as if they were built locally. 
> 
> This means you have to have the source path mapping worked out before
> you know what files are in the program, so it's hard to fix up later
> if you see a new unrelocated path.
> 

True and I was thinking further along these lines to enable rewriting existing paths in psymtabs/symtabs on demand (i.e. a command that would tell gdb: look through all psymtabs/symtabs and rewrite paths)... but wanted to get a feedback first :-)


  reply	other threads:[~2008-05-13 19:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 18:56 Aleksandar Ristovski
2008-05-13 19:00 ` Daniel Jacobowitz
2008-05-13 20:24   ` Aleksandar Ristovski
2008-05-13 21:11     ` Daniel Jacobowitz
2008-05-13 21:18       ` Aleksandar Ristovski [this message]
2008-05-13 21:40         ` Daniel Jacobowitz
2008-05-15 17:37           ` Daniel Jacobowitz
2008-05-15 19:29             ` Joel Brobecker
2008-05-15 19:30             ` Eli Zaretskii
2008-05-15 19:44               ` Daniel Jacobowitz
2008-05-15 22:40                 ` Eli Zaretskii
2008-05-16  0:28                   ` Daniel Jacobowitz
2008-05-16  8:15                     ` Aleksandar Ristovski
2008-05-16  8:19                       ` Aleksandar Ristovski
2008-05-16  8:21                       ` Daniel Jacobowitz
2008-05-16 15:26                         ` Mark Kettenis
2008-05-16 15:27                           ` Eli Zaretskii
2008-05-16 15:27                         ` Aleksandar Ristovski
2008-05-16 15:27                           ` Aleksandar Ristovski
2008-05-16 15:27                           ` Eli Zaretskii
2008-05-16 19:21                             ` Aleksandar Ristovski
2008-05-16 19:35                               ` Eli Zaretskii
2008-05-16 19:22                             ` Aleksandar Ristovski
2008-05-16 15:26                       ` Eli Zaretskii
2008-05-15 20:05               ` Joel Brobecker
2008-05-15 19:35             ` Aleksandar Ristovski
2008-05-17 19:49             ` Vladimir Prus
2008-05-19  4:12               ` Vladimir Prus
2008-05-13 21:12     ` Eli Zaretskii

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=4829E7DA.3010606@qnx.com \
    --to=aristovski@qnx.com \
    --cc=drow@false.org \
    --cc=gdb-patches@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