mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2025-03-13 13:49:00 +08:00
b0237c0eab
Before commit a8654e7d78 'Fixes PR 25475: ensure exec-file-mismatch "ask" always asks in case of mismatch', there was a difference in behaviour in test-case gdb.server/solib-list.exp. If the executable did not contain debug info (as is usually the case), gdb would detect a mismatch but not ask for confirmation: ... (gdb) target remote localhost:2346^M Remote debugging using localhost:2346^M warning: Mismatch between current exec-file solib-list^M and automatically determined exec-file /lib64/ld-2.26.so^M exec-file-mismatch handling is currently "ask"^M Reading symbols from /lib64/ld-2.26.so...^M Reading symbols from /usr/lib/debug/lib64/ld-2.26.so.debug...^M 0x00007ffff7dd7ea0 in _start () at rtld.c:745^M 745 }^M (gdb) PASS: gdb.server/solib-list.exp: non-stop 0: target remote ... If the executable did contain debug info (as happens to be the case for openSUSE), gdb would detect a mismatch and ask for confirmation: ... (gdb) PASS: gdb.server/solib-list.exp: non-stop 0: file binfile target remote localhost:2346^M Remote debugging using localhost:2346^M warning: Mismatch between current exec-file solib-list^M and automatically determined exec-file /lib64/ld-2.26.so^M exec-file-mismatch handling is currently "ask"^M Load new symbol table from "/lib64/ld-2.26.so"? (y or n) y^M Reading symbols from /lib64/ld-2.26.so...^M Reading symbols from /usr/lib/debug/lib64/ld-2.26.so.debug...^M 0x00007ffff7dd7ea0 in _start () at rtld.c:745^M 745 }^M (gdb) PASS: gdb.server/solib-list.exp: non-stop 0: target remote ... After commit a8654e7d78, the confirmation is now also asked in case there's no debug info. Tighten the test-case by verifying that the confirmation question is asked, as suggested in the log message of commit a8654e7d78: ... we can remove the bypass introduced by Tom in 6b9374f1, in order to always answer to the 'load' question. ... gdb/testsuite/ChangeLog: 2020-06-29 Tom de Vries <tdevries@suse.de> PR gdb/25475 * gdb.server/solib-list.exp: Verify that the symbol reload confirmation question is asked.
README for GNU development tools This directory contains various GNU compilers, assemblers, linkers, debuggers, etc., plus their support routines, definitions, and documentation. If you are receiving this as part of a GDB release, see the file gdb/README. If with a binutils release, see binutils/README; if with a libg++ release, see libg++/README, etc. That'll give you info about this package -- supported targets, how to use it, how to report bugs, etc. It is now possible to automatically configure and build a variety of tools with one command. To build all of the tools contained herein, run the ``configure'' script here, e.g.: ./configure make To install them (by default in /usr/local/bin, /usr/local/lib, etc), then do: make install (If the configure script can't determine your type of computer, give it the name as an argument, for instance ``./configure sun4''. You can use the script ``config.sub'' to test whether a name is recognized; if it is, config.sub translates it to a triplet specifying CPU, vendor, and OS.) If you have more than one compiler on your system, it is often best to explicitly set CC in the environment before running configure, and to also set CC when running make. For example (assuming sh/bash/ksh): CC=gcc ./configure make A similar example using csh: setenv CC gcc ./configure make Much of the code and documentation enclosed is copyright by the Free Software Foundation, Inc. See the file COPYING or COPYING.LIB in the various directories, for a description of the GNU General Public License terms under which you can copy the files. REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info on where and how to report problems.