public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/15472] New: Printing of "fullname" when the file is missing is causing problems for Eclipse
Date: Wed, 15 May 2013 21:22:00 -0000	[thread overview]
Message-ID: <bug-15472-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=15472

             Bug #: 15472
           Summary: Printing of "fullname" when the file is missing is
                    causing problems for Eclipse
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
        AssignedTo: unassigned@sourceware.org
        ReportedBy: dje@google.com
    Classification: Unclassified


We have a bug report where a user is seeing the following:

Can't find a source file at "/foo/bar/baz.cc"
Locate the file or edit the source lookup path to include its location.

The sources are in a different location from where they were originally
compiled when this happens.
The change in behaviour from 7.5 to 7.6 is that the output now includes
"fullname" even if the file isn't found, and I think(!) this is what causes
Eclipse trouble.

Repro:
[I'm using -fdebug-prefix-map and "b main" as a hack.  The real example does
something different.]

cd $HOME
gcc -g -fdebug-prefix-map=$HOME=. hello.c
cd /tmp
gdb -i=mi2 $HOME/a.out
[...]
b main
&"b main\n"
~"Breakpoint 1 at 0x4004f8: file hello.c, line 6.\n"
=breakpoint-created,bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="0x00000000004004f8",func="main",file="hello.c",fullname="./hello.c",line="6",thread-groups=["i1"],times="0",original-location="main"}
^done
(gdb)

With 7.5 the "fullname" field is elided and Eclipse uses the "file" field to
find hello.c. [Eclipse has its own source search path.]

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2013-05-15 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 21:22 dje at google dot com [this message]
2013-05-17 23:08 ` [Bug mi/15472] " dje at google dot com
2013-05-18  7:36 ` jan.kratochvil at redhat dot com

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=bug-15472-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).