public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Craig Jeffree <craig.jeffree@preston.net>, gdb@sources.redhat.com
Subject: Re: trouble locating source files through relative paths
Date: Tue, 23 Aug 2005 11:40:00 -0000	[thread overview]
Message-ID: <20050823114028.GB27899@white> (raw)
In-Reply-To: <20050823113138.GA27899@white>

On Tue, Aug 23, 2005 at 07:31:38AM -0400, Bob Rossi wrote:
> On Tue, Aug 23, 2005 at 03:03:29PM +1000, Craig Jeffree wrote:
> > On Fri, 2005-08-19 at 08:43 -0400, Bob Rossi wrote:
> > > What was the 'dir' command that you issued? What compiler are you using?
> > > Do you know what debug format you are using? (stabs or dwarf)?
> > 
> > The dir command that I issued was:
> > (gdb) dir /staff/taam/taam/bin/x86-Linux/nostrip/
> > Source directories searched: /staff/taam/taam/bin/x86-Linux/nostrip:
> > $cdir:$cwd
> > 
> > I'm using gcc 3.2.3 with the default debug format for x86-Linux (dwarf2
> > I believe).
> 
> Is this problem reproducable in a small example?

Geez, actually, I did just reproduce the problem. It seems that the only
current solution to get it to work is to do as you said, put the path to
where the include file is, not to where the relative path to it is.

I'll look into this.

Thanks,
Bob Rossi

  reply	other threads:[~2005-08-23 11:40 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 [this message]
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
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=20050823114028.GB27899@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).