From: Xavier de Gaye <xdegaye@gmail.com>
To: gdb@sourceware.org
Subject: inconsistency in gdb/mi -file-list-exec-source-files
Date: Thu, 29 Jul 2010 14:42:00 -0000 [thread overview]
Message-ID: <AANLkTimv=9t9fWPfFatwEaPS++PLj0O--j5EUs=PxvYz@mail.gmail.com> (raw)
The output of '-file-list-exec-source-files' differs between gdb 7.2 and
gdb previous releases: with gdb 7.2 the 'fullname' attribute becomes the
file basename and the 'file' attribute becomes the full pathname. It was
the reverse previously.
Xavier
=== GDB 7.2 ======================================
gdb/gdb-git/gdb/build/gdb/gdb --interpreter=mi
=thread-group-added,id="i1"
~"GNU gdb (GDB) 7.2.50.20100724-cvs\n"
~"Copyright (C) 2010 Free Software Foundation, Inc.\n"
~"License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>\nThis is free software: you are free
to change and redistribute it.\nThere is NO WARRANTY, to the extent
permitted by law. Type \"show copying\"\nand \"show warranty\" for
details.\n"
~"This GDB was configured as \"x86_64-unknown-linux-gnu\".\nFor bug
reporting instructions, please see:\n"
~"<http://www.gnu.org/software/gdb/bugs/>.\n"
(gdb)
-file-exec-and-symbols testsuite/foobar
^done
(gdb)
-file-list-exec-source-files
^done,files=[{file="",fullname="/home/aurel32/debian/co-packages/glibc/
glibc-2.7/build-tree/amd64-libc/csu/crtn.S"},{file="",fullname="bar.c"},
{file="/home/xavier/src/pyclewn-hg-working/testsuite/bar.c",fullname="bar.c"},
{file="",fullname="foo.c"},
{file="/home/xavier/src/pyclewn-hg-working/testsuite/foo.c",fullname="foo.c"},
{file="",fullname="foobar.c"},
{file="/home/xavier/src/pyclewn-hg-working/testsuite/foobar.c",fullname="foobar.c"},
{file="",fullname="/home/aurel32/debian/co-packages/glibc/glibc-2.7/build-tree/amd64-libc/csu/crti.S"},
{file="",fullname="init.c"}]
(gdb)
=== GDB 6.8 ======================================
/usr/bin/gdb --interpreter=mi
~"GNU gdb 6.8-debian\n"
~"Copyright (C) 2008 Free Software Foundation, Inc.\n"
~"License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>\n"
~"This is free software: you are free to change and redistribute it.\n"
~"There is NO WARRANTY, to the extent permitted by law. Type \"show
copying\"\n"
~"and \"show warranty\" for details.\n"
~"This GDB was configured as \"x86_64-linux-gnu\".\n"
(gdb)
-file-exec-and-symbols testsuite/foobar
^done
(gdb)
-file-list-exec-source-files
^done,files=[{file="/home/aurel32/debian/co-packages/glibc/glibc-2.7/build-tree/amd64-libc/csu/crtn.S"},
{file="bar.c"},
{file="bar.c",fullname="/home/xavier/src/pyclewn-hg-working/testsuite/bar.c"},
{file="foo.c"},
{file="foo.c",fullname="/home/xavier/src/pyclewn-hg-working/testsuite/foo.c"},
{file="foobar.c"},
{file="foobar.c",fullname="/home/xavier/src/pyclewn-hg-working/testsuite/foobar.c"},
{file="/home/aurel32/debian/co-packages/glibc/glibc-2.7/build-tree/amd64-libc/csu/crti.S"},{file="init.c"}]
(gdb)
next reply other threads:[~2010-07-29 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 14:42 Xavier de Gaye [this message]
2010-07-29 14:49 ` Daniel Jacobowitz
2010-07-30 19:22 ` Tom Tromey
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='AANLkTimv=9t9fWPfFatwEaPS++PLj0O--j5EUs=PxvYz@mail.gmail.com' \
--to=xdegaye@gmail.com \
--cc=gdb@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).