From: Kai Tietz <ktietz70@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch gdb]: Fix some DOS-path related issues in gdb
Date: Thu, 03 Mar 2011 13:48:00 -0000 [thread overview]
Message-ID: <AANLkTi=6FWfr9TaPD16V9x3eGh2Zzd-qBW8M0MmV=z-6@mail.gmail.com> (raw)
In-Reply-To: <E1Pv8WD-0006GH-Bc@fencepost.gnu.org>
2011/3/3 Eli Zaretskii <eliz@gnu.org>:
>> Date: Thu, 3 Mar 2011 13:10:13 +0100
>> From: Kai Tietz <ktietz70@googlemail.com>
>>
>> Sorry, first post were sent to wrong list. This patch fixes some
>> issues related to DOS file-system filenames and paths. I am not sure,
>> if I hit all places, nevertheless I am sure I hit most.
>> This patch uses the libiberty functions & macros about
>> directory-separator checks, absolute-path checks, and the
>> filename-comparision functions.
>
> The patch looks okay to me, but please do NOT install the changes for
> the following files, which cannot possibly meet with this issue:
> bsd-kvm.c, elfread.c, mdebugread.c, nto-procfs.c, rs6000-nat.c,
> xcoffread.c, fbsd-nat.c, linux-fork.c linux-nat.c, linux-thread-db,
> nto-tdep.c.
>
> Thanks for working on this.
>
Ok, the obvious native-parts - not using DOS-style file/paths - I
removed. The files elfread.c, mdebugread.c are also used for a x64
windows target, so I think those parts of patch should be kept. They
don't seem to be host-specific to me.
Regards,
Kai
next prev parent reply other threads:[~2011-03-03 13:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=QoOiBg3XmMv+hRNe8DkT2YiVGZ=7NhaQwzCey@mail.gmail.com>
2011-03-03 12:10 ` Kai Tietz
2011-03-03 13:24 ` Eli Zaretskii
2011-03-03 13:48 ` Kai Tietz [this message]
2011-03-03 14:00 ` Eli Zaretskii
2011-03-03 14:58 ` Joel Brobecker
2011-03-03 15:25 ` Kai Tietz
2011-03-03 15:32 ` Pedro Alves
2011-03-03 15:41 ` Kai Tietz
2011-03-03 16:09 ` Pedro Alves
2011-03-03 16:19 ` Kai Tietz
2011-03-03 16:42 ` Pedro Alves
2011-03-03 17:32 ` Kai Tietz
2011-03-04 7:23 ` Vladimir Simonov
2011-03-04 8:23 ` Joel Brobecker
2011-03-07 19:28 ` Jan Kratochvil
2011-03-07 19:28 ` Pedro Alves
2011-03-07 19:34 ` Jan Kratochvil
2011-03-03 18:09 ` Eli Zaretskii
2011-03-04 5:12 ` Joel Brobecker
2011-03-04 13:05 ` André Pönitz
2011-03-04 9:48 ` Kai Tietz
2011-03-04 10:37 ` Mark Kettenis
2011-03-05 9:13 ` Kai Tietz
2011-03-05 11:38 ` Vladimir Simonov
2011-03-05 12:45 ` Kai Tietz
2011-03-23 11:16 ` Kai Tietz
2011-03-23 12:44 ` Mark Kettenis
2011-03-23 14:07 ` Kai Tietz
2011-03-23 14:16 ` Pedro Alves
2011-03-23 14:18 ` Kai Tietz
2011-03-23 14:29 ` Pierre Muller
[not found] ` <-544184502231544940@unknownmsgid>
2011-03-23 14:44 ` Kai Tietz
2011-03-23 15:29 ` Pedro Alves
2011-03-23 15:29 ` Kai Tietz
2011-03-23 18:24 ` Eli Zaretskii
2011-03-23 21:11 ` Kai Tietz
2011-03-03 17:02 ` Mark Kettenis
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='AANLkTi=6FWfr9TaPD16V9x3eGh2Zzd-qBW8M0MmV=z-6@mail.gmail.com' \
--to=ktietz70@googlemail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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