Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kai Tietz <ktietz70@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mark.kettenis@xs4all.nl, gdb@sourceware.org
Subject: Re: [patch gdb]: Fix some DOS-path related issues in gdb
Date: Thu, 03 Mar 2011 13:21:00 -0000	[thread overview]
Message-ID: <AANLkTinAimN9LBz1GH_GJFiB8D8NosDbOv3swnpb4fYS@mail.gmail.com> (raw)
In-Reply-To: <E1Pv8LY-0005tI-7d@fencepost.gnu.org>

2011/3/3 Eli Zaretskii <eliz@gnu.org>:
>> Date: Thu, 3 Mar 2011 13:50:40 +0100
>> From: Kai Tietz <ktietz70@googlemail.com>
>> Cc: gdb@sourceware.org
>>
>> hmm, I admit that it is pretty unlikely that *nix-nat parts are used
>> with DOS-style paths. Nevertheless on cross-compiling from windows to
>> *nix such paths can happen easily.
>
> How can this happen, even for cross compilation?  Can you describe a
> use-case?

The debugging information (profiling, etc) are always using host's
file-names. So if you create a cross-compiler, the
file-name/path-information stored are always that one of the
host-system. Not of the target.
There is a need of having here some additional mapping features, but
this is for now not addressed by this patch.

For example, use a cross-compiler for windows-native on an unix-OS and
build an application with profiling and/or debugging. Then try to
debug/profile this app on a native windows host. You will notice that
filenames/paths are that one from the unix-OS and therefore are pretty
unusable on native Windows. (The other way around is of course the
same).

Kai


  reply	other threads:[~2011-03-03 13:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTi=QoOiBg3XmMv+hRNe8DkT2YiVGZ=7NhaQwzCey@mail.gmail.com>
2011-03-03 12:02 ` Kai Tietz
2011-03-03 12:15   ` Mark Kettenis
2011-03-03 12:50     ` Kai Tietz
2011-03-03 13:13       ` Eli Zaretskii
2011-03-03 13:21         ` Kai Tietz [this message]
2011-03-03 13:43           ` Andreas Schwab

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=AANLkTinAimN9LBz1GH_GJFiB8D8NosDbOv3swnpb4fYS@mail.gmail.com \
    --to=ktietz70@googlemail.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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