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: Thu, 25 Aug 2005 13:14:00 -0000 [thread overview]
Message-ID: <20050825111158.GA32174@white> (raw)
In-Reply-To: <1124928432.10500.12.camel@norman>
On Thu, Aug 25, 2005 at 10:07:12AM +1000, Craig Jeffree wrote:
> On Wed, 2005-08-24 at 07:24 -0400, Bob Rossi wrote:
> > 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.
>
> Both before and after I do the 'dir' command 'info sources' spits out
> the filename with no path at all.
>
> >
> > 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?
>
> When I do 'list GeAttribute.H:1' in my application GDB fails to find the
> file after trying 'GeAttribute.H' in the directory I specified with
> 'dir' and my cwd. It also tries
> '../../../include/General/GeAttribute.H'. I can't say I know where it
> figures out this relative path from because 'info sources' doesn't
> mention it, however that path is correct when taken from the location of
> the binary (the path I gave to 'dir').
>
> If I try 'list ../../../include/General/GeAttribute.H:1' it says:
> 'No source file named ../../../include/General/GeAttribute.H.'
Hi Craig,
Thanks for all the explaining. I have yet another question. Does
GeAttribute.H also have a counterpart GeAttribute.cpp? If so, is that
file found by GDB before or after the dir command? I appreciate the
response's because the examples I reproduce are slightly different then
what you are seeing, although it might be enough to prove the point.
Thanks,
Bob Rossi
next prev parent reply other threads:[~2005-08-25 13:14 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
2005-08-25 0:07 ` Craig Jeffree
2005-08-25 13:14 ` Bob Rossi [this message]
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=20050825111158.GA32174@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).