From: Eli Zaretskii <eliz@gnu.org>
To: danny.backx@scarlet.be
Cc: tromey@redhat.com, gdb@sourceware.org
Subject: Re: Build question
Date: Sat, 22 Aug 2009 11:07:00 -0000 [thread overview]
Message-ID: <83skfkfa4n.fsf@gnu.org> (raw)
In-Reply-To: <1250931899.11282.142.camel@pavilion>
> From: Danny Backx <danny.backx@scarlet.be>
> Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
> Date: Sat, 22 Aug 2009 11:04:58 +0200
>
> 1. The one I suggested earlier. May not be the right solution.
> 2. Generalize target filename handling in gdb. Might be much harder than
> expected.
> 3. Separate directory and file name in the communication between
> gdbserver and gdb, so mixup 2 is avoided.
> 4. Extend gdbserver/gdb communication so the target file name syntax
> is reported back.
> 5. Do (4) but in gdb target properties (this may be what Eli said).
> Would require extending the gdb target definitions.
>
> Comments ?
Can you point out the places in the code (hopefully, not too many)
where the Posix assumption about file-name syntax needs to be replaced
with the Windows assumption?
If there are not too many of them, we could modify them to use one or
two user options. For starters, these options would need to be set
manually, by the user who knows what filesystem she is working with.
Later, we could try to set them automatically.
WDYT?
next prev parent reply other threads:[~2009-08-22 9:55 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
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 [this message]
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=83skfkfa4n.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