From: Daniel Jacobowitz <dan@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: [gdb/libiberty] Improve support for cross debugging shared libraries with DOS style pathnames (from Unix hosts)
Date: Thu, 22 Apr 2010 17:46:00 -0000 [thread overview]
Message-ID: <20100422174610.GA7820@caradoc.them.org> (raw)
In-Reply-To: <201004221824.27019.pedro@codesourcery.com>
On Thu, Apr 22, 2010 at 06:24:26PM +0100, Pedro Alves wrote:
> (At some point, this patch also included a new user knob
> to make source file name comparision flavour (and
> mostly s/FILENAME_CMP/source_filename_cmp/,
> s/lbasename/source_lbasename throught the sources/debug info
> handling parts of GDB.) depend on build file system. That's because
> often you stumble on the fact that cross debugging a Windows/SymbianOS
> binary _built_ on non-Unix, includes `\' in debug info, and a Unix
> GDB can't grok that. I mention this, in case someone would
> suggest this new setting should be more general and cover that
> case as well. It shouldn't: the concepts are different --- target
> paths, vs source/debug info/build paths, and you'll want to be
> able to tweak them independently.)
I agree with this patch's approach, and with this separation. One
important way that source paths are different: a host path is clearly
either Unix or DOS. A target path, ditto. A source path, not so
much. It is common to have half and half, e.g. if your toolchain was
built on Linux but ran on Windows.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2010-04-22 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 17:24 Pedro Alves
2010-04-22 17:46 ` Daniel Jacobowitz [this message]
2010-04-23 8:54 ` Eli Zaretskii
2010-04-23 10:46 ` Pedro Alves
2010-04-23 11:15 ` Mark Kettenis
2010-04-23 14:30 ` Eli Zaretskii
2010-04-23 15:41 ` Mark Kettenis
2010-04-23 14:35 ` Eli Zaretskii
2010-04-24 11:18 ` Pedro Alves
2010-04-24 11:40 ` Eli Zaretskii
2010-04-24 13:13 ` Pedro Alves
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=20100422174610.GA7820@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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