From: "José Miguel" <jmiguelbenitez@supercable.es>
To: gdb@sources.redhat.com
Subject: Re: Compilation directories
Date: Thu, 07 Oct 2004 12:23:00 -0000 [thread overview]
Message-ID: <200410071257.21085.jmiguelbenitez@supercable.es> (raw)
In-Reply-To: <20041006133927.GA22197@nevyn.them.org>
On Wednesday 06 October 2004 15:39, Daniel Jacobowitz wrote:
> On Wed, Oct 06, 2004 at 10:36:49AM +0200, José Miguel wrote:
> > On Wednesday 06 October 2004 04:18, Daniel Jacobowitz wrote:
> > > There is no way to do it. $cdir isn't a convenience variable, because
> > > there's no way for convenience variables to represent strings today.
> > > It's just text substitution in the source path searching.
> >
> > So, is there any way to work with absolute paths? I mean, if I'm
> > debugging a program
> > mcore-elf-gdb sample.elf
> > and I type
> > info sources
> > I get no information about paths
> > main.c, set_led.c
> > This is always that way although executable file and sources are in
> > different directories. I know gdb knows where to find the source files
> > because if I type
> > info source main
> > gdb asks me
> > Current source file is main.c
> > Compilation directory is /home/matt/proyecto/gnusample
> > Located in /home/matt/proyecto/gnusample/main.c
> > Then, my question is if there's a way to get something like
> > info sources
> > /home/matt/proyecto/gnusample/main.c,
> > /home/matt/proyecto/gnusample/set_led.c I'm trying to make a front end
> > for gdb, so if I want to show the source files I need to know where to
> > find them.
>
> I recommend you use GDB 6.2, and the MI command
> -file-list-exec-source-files. You want the "fullname" portion of the
> output.
That's exactly what I want. Thank you very much.
Jose Miguel
prev parent reply other threads:[~2004-10-07 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 11:52 José Miguel
2004-10-06 2:00 ` Andrew Cagney
2004-10-06 2:59 ` Daniel Jacobowitz
2004-10-06 10:01 ` José Miguel
2004-10-06 13:40 ` Daniel Jacobowitz
2004-10-07 12:23 ` José Miguel [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=200410071257.21085.jmiguelbenitez@supercable.es \
--to=jmiguelbenitez@supercable.es \
--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