public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Craig Jeffree <craig.jeffree@preston.net>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: trouble locating source files through relative paths
Date: Fri, 26 Aug 2005 03:35:00 -0000	[thread overview]
Message-ID: <1125027325.10500.82.camel@norman> (raw)
In-Reply-To: <20050826022000.GA1699@white>

On Thu, 2005-08-25 at 22:20 -0400, Bob Rossi wrote:
> OK, thanks. Is there any .cpp files that are in the relative directory? I
> want to know if GDB can find the .cpp files but not the .H files. So, do
> 'info sources' before the dir command and check to see if the .cpp files
> from the relative directory have an absolute path to them. If not, do the
> dir command, and then see. Thanks.

Unfortunately no.  Our build system "installs" header files into a
common include directory and this include directory is specified as a
relative path in the -I option to g++.  The actual compilation units are
always specified to g++ simply by filename as they are always in the
current working directory since make changes to that directory.

Cheers,
Craig.

      reply	other threads:[~2005-08-26  3:35 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
2005-08-25 23:43                 ` Craig Jeffree
2005-08-26  2:20                   ` Bob Rossi
2005-08-26  3:35                     ` Craig Jeffree [this message]

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=1125027325.10500.82.camel@norman \
    --to=craig.jeffree@preston.net \
    --cc=bob@brasko.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).