public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: nixahn <nixahn@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: control debug information source path
Date: Wed, 28 Dec 2011 19:17:00 -0000	[thread overview]
Message-ID: <33044253.post@talk.nabble.com> (raw)


Hi, this is my first post in this forum; I am having problems with the stored
debugging information; I have 2 different platforms running gcc 4.1 and 4.6
which behave differently. In one, when I compile a binary using a static
library, the source files for the library are stored with their absolute
paths. this is useful because gdb then finds the source files automatically.
in the 4.1 platform (a rocks cluster with redhat) the source files info is
stored only by name, without paths. I know I could try to add the directory
for the source files with gdb, the problem is that the library is gsl and
the source files are in many subdirectories, making it problematic to
specify all of them to gdb. it would be great if I knew how to control
whether gcc stores absoulute source paths in the debugging information. is
this related to the debug format? when building my binary and gsl, I always
use the -g option, but since both platforms are linux they should be using
stabs according to the little I read.

Anyhow, I hope someone can point me in the right direction... thanks in
advance
-- 
View this message in context: http://old.nabble.com/control-debug-information-source-path-tp33044253p33044253.html
Sent from the gcc - Help mailing list archive at Nabble.com.

             reply	other threads:[~2011-12-28  3:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 19:17 nixahn [this message]
2011-12-31  2:05 ` Juan Ramírez

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=33044253.post@talk.nabble.com \
    --to=nixahn@gmail.com \
    --cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).