From: Eli Zaretskii <eliz@gnu.org>
To: danny.backx@scarlet.be
Cc: tromey@redhat.com, gdb@sourceware.org
Subject: Re: Build question
Date: Fri, 21 Aug 2009 18:51:00 -0000 [thread overview]
Message-ID: <83ab1tgh9h.fsf@gnu.org> (raw)
In-Reply-To: <1250877901.11282.116.camel@pavilion>
> From: Danny Backx <danny.backx@scarlet.be>
> Cc: tromey@redhat.com, gdb@sourceware.org
> Date: Fri, 21 Aug 2009 20:05:00 +0200
>
> On Fri, 2009-08-21 at 20:31 +0300, Eli Zaretskii wrote:
> > > From: Tom Tromey <tromey@redhat.com>
> > > I am not familiar with this area in depth. From what you've said it
> > > sounds like gdb has some confusion about host paths and target paths.
> >
> > The way these macros and the corresponding source fragments in GDB are
> > set, they only DTRT for native debugging.
>
> Also right, but it looks like it doesn't take much to make it just work.
I think they need to be converted to run-time tests instead. For
that, we would probably need some kind of primitive that returns the
filesystem type of the target, what the macros do now at compile-time.
next prev parent reply other threads:[~2009-08-21 18:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 0:24 Danny Backx
2009-08-21 17:30 ` Tom Tromey
2009-08-21 17:57 ` Eli Zaretskii
2009-08-21 18:23 ` Danny Backx
2009-08-21 18:51 ` Eli Zaretskii [this message]
2009-08-21 20:15 ` Danny Backx
2009-08-21 21:57 ` Eli Zaretskii
2009-08-22 9:03 ` Tom Tromey
2009-08-22 9:55 ` Danny Backx
2009-08-22 11:07 ` Eli Zaretskii
2009-08-24 10:11 ` Danny Backx
2009-09-01 18:03 ` Danny Backx
2009-09-01 19:34 ` Eli Zaretskii
2009-09-01 20:10 ` Danny Backx
2009-09-02 3:25 ` Eli Zaretskii
2009-09-05 9:33 ` Danny Backx
2009-09-01 19:35 ` Eli Zaretskii
2009-08-22 22:01 ` Daniel Jacobowitz
2009-08-23 7:28 ` Joel Brobecker
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=83ab1tgh9h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=danny.backx@scarlet.be \
--cc=gdb@sourceware.org \
--cc=tromey@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