public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Show line numbers in output for "info var/func/type" Date: Fri, 13 Apr 2018 17:44:00 -0000 [thread overview] Message-ID: <b744723f571815e6cee43df371c8e733e34e1edf@gdb-build> (raw) *** TEST RESULTS FOR COMMIT b744723f571815e6cee43df371c8e733e34e1edf *** Author: Andreas Arnez <arnez@linux.vnet.ibm.com> Branch: master Commit: b744723f571815e6cee43df371c8e733e34e1edf Show line numbers in output for "info var/func/type" The GDB commands "info variables", "info functions", and "info types" show the appropriate list of definitions matching the given pattern. They also group them by source files. But no line numbers within these source files are shown. The line number information is particularly useful to the user when a simple "grep" doesn't readily point to a definition. This is often the case when the definition involves a macro, occurs within a namespace, or when the identifier appears very frequently in the source file. This patch enriches the printout of these commands by the line numbers and adjusts affected test cases to the changed output where necessary. The new output looks like this: (gdb) i variables All defined variables: File foo.c: 3: const char * const foo; 1: int x; The line number is followed by a colon and a tab character, which is then followed by the symbol definition. If no line number is available, the tab is printed out anyhow, so definitions line up. gdb/ChangeLog: * symtab.c (print_symbol_info): Precede the symbol definition by the line number when available. * NEWS: Advertise this enhancement. gdb/doc/ChangeLog: * gdb.texinfo (Symbols): Mention the fact that "info variables/functions/types" show source files and line numbers. gdb/testsuite/ChangeLog: * gdb.ada/info_types.exp: Adjust expected output to the line numbers now printed by "info var/func/type". * gdb.base/completion.exp: Likewise. * gdb.base/included.exp: Likewise. * gdb.cp/cp-relocate.exp: Likewise. * gdb.cp/cplusfuncs.exp: Likewise. * gdb.cp/namespace.exp: Likewise. * gdb.dwarf2/dw2-case-insensitive.exp: Likewise.
next reply other threads:[~2018-04-13 17:44 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-13 17:44 sergiodj+buildbot [this message] 2018-04-13 17:44 ` *** COMPILATION FAILED *** Failures on NetBSD-x86_64-m64, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-13 17:48 ` Failures on Fedora-x86_64-m64, branch master sergiodj+buildbot 2018-04-13 17:49 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-04-13 17:50 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-04-13 17:53 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-04-13 18:03 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot 2018-04-13 18:05 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-04-13 18:07 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-13 18:07 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-04-13 18:08 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-04-13 18:14 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot 2018-04-13 18:17 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-04-13 18:21 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-04-13 18:25 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-04-13 18:36 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-04-13 19:57 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-04-13 20:40 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-04-13 21:23 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
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=b744723f571815e6cee43df371c8e733e34e1edf@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@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: linkBe 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).