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: Mon, 07 Jan 2008 21:32:00 -0000 [thread overview]
Message-ID: <u7iiltjbz.fsf@gnu.org> (raw)
In-Reply-To: <e394668d0801070935k1bbfd41cmc573f8dd9b934c70@mail.gmail.com> (dje@google.com)
> Date: Mon, 7 Jan 2008 09:35:30 -0800
> From: "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
>
> On Jan 6, 2008 8:17 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > > Date: Sun, 6 Jan 2008 13:07:25 -0800
> > > From: "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
> > >
> > > What would the option apply to? How would the user know when and when
> > > not to use it?
> >
> > I don't really understand the question. How would the user know when
> > to use any other option? If they read the documentation and
> > understand the issues, they will know.
>
> I realize the question may sound odd. I asked it because the range to
> which the option may apply seems vast, whereas the range to which it
> will be applied (AIUI) seems small, leading to excessive confusion.
Many GDB options are used only in very rare cases. That doesn't make
them less useful: when you are in that rare situation, these options
are a godsend.
> Perhaps I should have written "gdb
> prog.with.other.path.format.in.debug.info". :-)
> As a datapoint, and to give some context for the above, I patched
> filenames.h to print a message whenever IS_ABSOLUTE_PATH is called.
>
> dje@ruffy:~$ ./gdb -nx hello
> GNU gdb 6.7.50.20080104-cvs
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-linux"...
> IS_ABSOLUTE_PATH (/home/dje/hello.x32)
> IS_ABSOLUTE_PATH (/home/dje/hello.x32)
> IS_ABSOLUTE_PATH (start.S)
> IS_ABSOLUTE_PATH (../sysdeps/i386/elf/start.S)
> IS_ABSOLUTE_PATH (crti.S)
> IS_ABSOLUTE_PATH (/build/buildd/glibc-2.3.6/build-tree/i386-libc/csu/crti.S)
> IS_ABSOLUTE_PATH (hello.c)
> IS_ABSOLUTE_PATH (hello.c)
> IS_ABSOLUTE_PATH (crtn.S)
> IS_ABSOLUTE_PATH (/build/buildd/glibc-2.3.6/build-tree/i386-libc/csu/crtn.S)
What GDB code causes these calls, and why?
next prev parent reply other threads:[~2008-01-07 21:32 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
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 [this message]
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=u7iiltjbz.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