From: Bob Rossi <bob@brasko.net>
To: Craig Jeffree <craig.jeffree@preston.net>
Cc: gdb@sources.redhat.com
Subject: Re: trouble locating source files through relative paths
Date: Wed, 24 Aug 2005 11:24:00 -0000 [thread overview]
Message-ID: <20050824112417.GA30211@white> (raw)
In-Reply-To: <1124866437.3749.75.camel@norman>
On Wed, Aug 24, 2005 at 04:53:57PM +1000, Craig Jeffree wrote:
> On Tue, 2005-08-23 at 07:40 -0400, Bob Rossi wrote:
> > I'll look into this.
>
> It looks like find_and_open_source() could be modified to check if
> dirname is relative and if so call openp with dirname prepended to
> filename instead of modifying the search path.
>
> I think this is what Dave Korn suggested earlier, except he proposes
> identifying the relative link before the call to find_and_open_source
> and avoiding the split at that point. However, this might result in
> checks occuring in multiple places - I haven't looked for this.
>
> I'm not familiar with the gdb source so I'm not sure which solution will
> be more appropriate. Putting the fix in find_and_open_source() would be
> more self contained, however this might affect other clients of
> find_and_open_source() in ways I haven't considered.
Well, I haven't had enough time to investigate this more, however, I did
find some odd results with the example I came up with. For example, if
I do 'info sources' before the dir command is applied, GDB spits out the
relative path. However, if I do the dir command, and then do 'info
sources', then GDB spits out the absolute path.
Once GDB has the absolute path, if I then do 'list uut.h:1', GDB can
still not find the file. If I do 'list ../include/uut.h:1',
then I get an Internal GDB error. Do you get these same results?
If so, find_and_open_source is finding the fullname, even though things
are still not working properly. Hopefully I'll have more time to look
into this today.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2005-08-24 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 7:25 Craig Jeffree
2005-08-19 12:43 ` Bob Rossi
2005-08-23 5:04 ` Craig Jeffree
2005-08-23 9:20 ` Dave Korn
2005-08-23 11:31 ` Bob Rossi
2005-08-23 11:40 ` Bob Rossi
2005-08-23 14:49 ` Daniel Jacobowitz
2005-08-23 15:24 ` Bob Rossi
2005-08-24 6:55 ` Craig Jeffree
2005-08-24 11:24 ` Bob Rossi [this message]
2005-08-25 0:07 ` Craig Jeffree
2005-08-25 13:14 ` Bob Rossi
2005-08-25 23:43 ` Craig Jeffree
2005-08-26 2:20 ` Bob Rossi
2005-08-26 3:35 ` Craig Jeffree
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=20050824112417.GA30211@white \
--to=bob@brasko.net \
--cc=craig.jeffree@preston.net \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).