Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: aristovski@qnx.com, gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: Re: [RFC] new substitute path when loading feature
Date: Fri, 16 May 2008 15:26:00 -0000	[thread overview]
Message-ID: <200805152004.m4FK4n82007876@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20080515194418.GA17618@caradoc.them.org> (message from Daniel 	Jacobowitz on Thu, 15 May 2008 15:44:18 -0400)

> Date: Thu, 15 May 2008 15:44:18 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 
> On Thu, May 15, 2008 at 03:40:26PM -0400, Aleksandar Ristovski wrote:
> > You will probably want this wrapped in an if. In fact, I don't see
> > how will it work properly with only one flag - we probably don't
> > want to do case-insensitive compare by default, but we do need to
> > compare case insensitive for dos-like file system.
> 
> Is this really necessary?  As long as everything gives GDB the same
> capitalization of the file (including debug info and any front end),
> then we don't need to be case insensitive.
> 
> If you think this is an important feature I can make the variable
> tri-state:
> 
> set support-dos-filenames (on|off|auto)
> 
> Auto would be case sensitive on POSIX hosts, on wouldn't, auto would
> be the default.

Sorry, but I think this really is a bad idea.  For a native debugger
on a POSIX system I really don't want the oddities of dos-like filenames.


  reply	other threads:[~2008-05-15 20:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13 18:56 Aleksandar Ristovski
2008-05-13 19:00 ` Daniel Jacobowitz
2008-05-13 20:24   ` Aleksandar Ristovski
2008-05-13 21:11     ` Daniel Jacobowitz
2008-05-13 21:18       ` Aleksandar Ristovski
2008-05-13 21:40         ` Daniel Jacobowitz
2008-05-15 17:37           ` Daniel Jacobowitz
2008-05-15 19:29             ` Joel Brobecker
2008-05-15 19:30             ` Eli Zaretskii
2008-05-15 19:44               ` Daniel Jacobowitz
2008-05-15 22:40                 ` Eli Zaretskii
2008-05-16  0:28                   ` Daniel Jacobowitz
2008-05-16  8:15                     ` Aleksandar Ristovski
2008-05-16  8:19                       ` Aleksandar Ristovski
2008-05-16  8:21                       ` Daniel Jacobowitz
2008-05-16 15:26                         ` Mark Kettenis [this message]
2008-05-16 15:27                           ` Eli Zaretskii
2008-05-16 15:27                         ` Aleksandar Ristovski
2008-05-16 15:27                           ` Eli Zaretskii
2008-05-16 19:21                             ` Aleksandar Ristovski
2008-05-16 19:35                               ` Eli Zaretskii
2008-05-16 19:22                             ` Aleksandar Ristovski
2008-05-16 15:27                           ` Aleksandar Ristovski
2008-05-16 15:26                       ` Eli Zaretskii
2008-05-15 20:05               ` Joel Brobecker
2008-05-15 19:35             ` Aleksandar Ristovski
2008-05-17 19:49             ` Vladimir Prus
2008-05-19  4:12               ` Vladimir Prus
2008-05-13 21:12     ` Eli Zaretskii

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=200805152004.m4FK4n82007876@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=aristovski@qnx.com \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.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