From: "Doug Evans" <dje@google.com>
To: "Eli Zaretskii" <eliz@gnu.org>
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 21:07:00 -0000 [thread overview]
Message-ID: <e394668d0801061307x57c030frc9791d9cffef5a67@mail.gmail.com> (raw)
In-Reply-To: <uir26u2sj.fsf@gnu.org>
On Jan 6, 2008 12:17 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > How would this option work in practice?
>
> How about
>
> (gdb) set filename-style (dos|unix)
>
> ?
Apologies. The question on how it would work in practice and the
comment on being cumbersome weren't intended to be treated in
isolation.
> > 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.
I haven't used demangle-style enough to know if the use-cases are similar.
What would the option apply to? How would the user know when and when
not to use it?
One thing that occurs to me is what if I do "bash$ gdb
/prog/with/other/path/format"? Will gdb need to know the format
before the user gets a chance to specify the format? [Now we're not
just adding an option but a command line parameter too.]
Another thing that occurs to me is that I vaguely remember building
libraries in one environment and then using the library in another. I
could be mistaken, it's been awhile. Can one have a case where both
path formats are in use simultaneously?
I don't mean to belabor the issue. It's just that an option seems
problematic at best. I could be wrong of course.
next prev parent reply other threads:[~2008-01-06 21:07 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
2008-01-06 21:07 ` Doug Evans [this message]
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=e394668d0801061307x57c030frc9791d9cffef5a67@mail.gmail.com \
--to=dje@google.com \
--cc=ARistovski@qnx.com \
--cc=RMansfield@qnx.com \
--cc=drow@false.org \
--cc=eliz@gnu.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