Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Bob Rossi <bob_rossi@cox.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB/MI absolute path
Date: Thu, 06 Feb 2003 22:13:00 -0000	[thread overview]
Message-ID: <1044569850.2029.144.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <20030206215525.GC7441@white>

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
desinged to work with an IDE, not just a standalone 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.

Of course, I think we'll all agree that #2 is preferred. This is the
route we took in Insight (see
gdbtk/generic/gdbtk-cmds.c:gdb_find_file_command).

Phew! After saying all that, the real response to your question is:
"It's a bug: open a new bug report." :-(

Keith



  reply	other threads:[~2003-02-06 22:13 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 [this message]
2003-02-07 13:06   ` Bob Rossi
     [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=1044569850.2029.144.camel@lindt.uglyboxes.com \
    --to=keiths@redhat.com \
    --cc=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