From: Bob Rossi <bob_rossi@cox.net>
To: gdb@sources.redhat.com
Subject: Re: GDB/MI absolute path
Date: Fri, 07 Feb 2003 13:06:00 -0000 [thread overview]
Message-ID: <20030207130652.GB7980@white> (raw)
In-Reply-To: <1044569850.2029.144.camel@lindt.uglyboxes.com>
Thanks for the great answer.
On Thu, Feb 06, 2003 at 02:17:30PM -0800, Keith Seitz wrote:
> On Thu, 2003-02-06 at 13:55, Bob Rossi wrote:
> > Also, what is the best way to ask mi for the absolute path to the
> > current source file. This wasn't a problem using annotate 1 or 2, and I
> > can't figure out how to get it using mi.
>
> This is a known (to me) problem with MI. The problem is that MI was
> designed to work with an IDE, not just a stand-alone GUI for the
> debugger. In the case of an IDE, this information isn't needed, since
> the IDE knows everything there is to know about files.
>
> However, like Insight, cgdb will need some way of turning
> "../foo/bar/baz.c" into "/home/a/b/c/foo/bar/baz.c". There are two
> options (excluding hacks around the problem):
>
> 1. Get the complete source search path from GDB and let the GUI search
> for the file. This means the GUI writer would also need the compile
> directory for each file.
>
> 2. Get GDB to tell you where it thinks a file is located.
I would like to write a patch to GDB/MI and send it in with a bug
report. Does any of the GDB/MI maintainers know if the current design
model of GDB/MI would prefer an implicit return of the current
absolute path ( like annotations ) or an explicit return ( the GUI
requests it every time via a new GDB/MI command).
Thanks
Bobby
next prev parent reply other threads:[~2003-02-07 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 21:55 Bob Rossi
2003-02-06 22:13 ` Keith Seitz
2003-02-07 13:06 ` Bob Rossi [this message]
[not found] <1044623213.10462.ezmlm@sources.redhat.com>
2003-02-07 18:04 ` Jim Ingham
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=20030207130652.GB7980@white \
--to=bob_rossi@cox.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