From: Eli Zaretskii <eliz@gnu.org>
To: "Doug Evans" <dje@google.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com,
ARistovski@qnx.com, gcc-patches@gcc.gnu.org,
RMansfield@qnx.com
Subject: Re: [patch] IS_ABSOLUTE_PATH to handle both DOS and POSIX path st yles
Date: Sun, 06 Jan 2008 20:18:00 -0000 [thread overview]
Message-ID: <uir26u2sj.fsf@gnu.org> (raw)
In-Reply-To: <e394668d0801061203u5c582be7m9f78cb5d4fdd3bc7@mail.gmail.com> (dje@google.com)
> Date: Sun, 6 Jan 2008 12:03:08 -0800
> From: "Doug Evans" <dje@google.com>
> Cc: "Daniel Jacobowitz" <drow@false.org>, gdb-patches@sources.redhat.com,
> ARistovski@qnx.com, gcc-patches@gcc.gnu.org, RMansfield@qnx.com
>
> > In that case, I think it's wrong to allow both styles of slashes and
> > absolute file names. Instead, we should have a user option to set the
> > correct style, which would default to the convention of the platform
> > where GDB was built to run.
> >
> > If you agree with this approach, then the _ANY version of the macros
> > is not needed.
>
> It seems like GDB should know what to use, or at least be able to
> figure it out (in cases where it really matters).
How can GDB figure that out? We don't tell it enough about the
program being debugged for that.
But if I'm wrong, and GDB _can_ figure it out on its own, then it
should use the right style of file names automagically, and the _ANY
set of macros is again not needed.
> Are we really sure we need an option?
If GDB cannot figure this out, the user should tell it, since the user
always knows.
> How would this option work in practice?
How about
(gdb) set filename-style (dos|unix)
?
> If one ever wanted to set it to the non-default value it'd be
> rather cumbersome to have to set it and then reset it for one-off
> uses of "the other" path kind.
No more cumbersome than any other similar option, like "set
demangle-style", for example.
next prev parent reply other threads:[~2008-01-06 20:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2F6320727174C448A52CEB63D85D11F40A58@nova.ott.qnx.com>
[not found] ` <20080106054030.GA10410@caradoc.them.org>
2008-01-06 19:38 ` Eli Zaretskii
2008-01-06 20:03 ` Doug Evans
2008-01-06 20:18 ` Eli Zaretskii [this message]
2008-01-06 21:07 ` Doug Evans
2008-01-07 3:40 ` Daniel Jacobowitz
2008-01-07 4:21 ` Eli Zaretskii
2008-01-07 13:17 ` Daniel Jacobowitz
2008-01-07 21:28 ` Eli Zaretskii
2008-01-07 4:18 ` Eli Zaretskii
2008-01-07 17:36 ` Doug Evans
2008-01-07 21:32 ` Eli Zaretskii
2008-01-07 21:36 ` Daniel Jacobowitz
2008-01-08 4:25 ` Eli Zaretskii
2008-01-08 13:47 ` Daniel Jacobowitz
2008-01-09 16:13 Aleksandar Ristovski
2008-01-09 19:10 ` Eli Zaretskii
2008-01-09 19:43 ` Daniel Jacobowitz
2008-01-10 4:13 ` Eli Zaretskii
2008-01-10 14:01 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2008-01-04 19:26 Aleksandar Ristovski
2008-01-04 19:33 ` Daniel Jacobowitz
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=uir26u2sj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ARistovski@qnx.com \
--cc=RMansfield@qnx.com \
--cc=dje@google.com \
--cc=drow@false.org \
--cc=gcc-patches@gcc.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