From: Frederic RISS <frederic.riss@st.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Don't lose compilation directory in Dwarf2 line-tables
Date: Fri, 14 Apr 2006 11:44:00 -0000 [thread overview]
Message-ID: <1145015039.14807.767.camel@crx549.cro.st.com> (raw)
In-Reply-To: <u1ww035rv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
On Fri, 2006-04-14 at 11:44 +0300, Eli Zaretskii wrote:
> In addition, I think the current algorithm for searching the sources
> is described in the user's manual; please see if there's something in
> that description that needs to be updated with your changes.
I looked at it (7.4 Specifying source directories). The algorithm that
is described is the one in lookup_(partial_)symtab, and I don't think
I'll change that (my patch only modifies the dwarf2 line-info reading).
While reading that part, I think that I spotted a very minor issue. One
sentence there reads :
« Note that the executable search path is not used to locate the source
ï¬les. Neither is the current working directory, unless it happens to be
in the source path. »
Which isn't false, but I don't think that the user has the ability to
specify an empty source path, it at least always contains $cdir and
$cwd. This means that the current working directory will always be used
to locate source files.
Also there are 2 mentions below that to 'resetting the source path to
empty', but as I said, the source path is never really empty.
If I'm not mistaken and if its not too much nitpicking, shall I commit
something like the attached patch?
[-- Attachment #2: doc.patch --]
[-- Type: text/x-patch, Size: 1403 bytes --]
2006-04-14 Frederic Riss <frederic.riss@st.com>
* gdb.texinfo (Specifying source directories): Update the description
of the source file search to reflect the fact that the source path
always contains at least $cdir and $cwd.
--- gdb.texinfo.orig 2006-04-14 13:18:53.000000000 +0200
+++ gdb.texinfo 2006-04-14 13:34:08.000000000 +0200
@@ -5005,8 +5005,7 @@
that---@file{/mnt/cross/foo.c}.
Note that the executable search path is @emph{not} used to locate the
-source files. Neither is the current working directory, unless it
-happens to be in the source path.
+source files.
Whenever you reset or rearrange the source path, @value{GDBN} clears out
any information it has cached about where source files are found and where
@@ -5048,7 +5047,7 @@
directory at the time you add an entry to the source path.
@item directory
-Reset the source path to empty again. This requires confirmation.
+Reset the source path to its initial value. This requires confirmation.
@c RET-repeat for @code{directory} is explicitly disabled, but since
@c repeating it would be a no-op we do not say that. (thanks to RMS)
@@ -5064,7 +5063,7 @@
@enumerate
@item
-Use @code{directory} with no argument to reset the source path to empty.
+Use @code{directory} with no argument to reset the source path to its initial value.
@item
Use @code{directory} with suitable arguments to reinstall the
next prev parent reply other threads:[~2006-04-14 11:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 11:25 [RFC] Don't loose " Frederic RISS
2006-04-13 17:49 ` Jim Blandy
2006-04-14 7:32 ` [RFC] Don't lose " Frederic RISS
2006-04-14 7:41 ` Jim Blandy
2006-04-14 8:23 ` Frederic RISS
2006-04-14 14:04 ` Daniel Jacobowitz
2006-04-14 14:51 ` Frederic RISS
2006-04-18 12:32 ` Frederic RISS
2006-04-18 13:04 ` Daniel Jacobowitz
2006-04-18 14:00 ` Frederic RISS
2006-04-20 16:27 ` Daniel Jacobowitz
2006-04-21 7:14 ` Frederic RISS
2006-04-21 1:10 ` Jim Blandy
2006-04-21 8:35 ` Frederic RISS
2006-04-21 16:46 ` Jim Blandy
2006-04-21 17:00 ` Frederic RISS
2006-04-24 12:49 ` Andrew STUBBS
2006-04-14 8:44 ` Eli Zaretskii
2006-04-14 11:44 ` Frederic RISS [this message]
2006-04-14 13:08 ` Eli Zaretskii
2006-04-14 13:42 ` Frederic RISS
2006-04-14 14:21 ` Eli Zaretskii
2006-04-14 14:58 ` Daniel Jacobowitz
2006-04-14 15:03 ` Eli Zaretskii
2006-04-14 18:39 ` Frédéric Riss
2006-04-13 19:58 ` [RFC] Don't loose " Jason Molenda
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=1145015039.14807.767.camel@crx549.cro.st.com \
--to=frederic.riss@st.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