mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-06-25 04:49:54 +08:00

When running test-case gdb.linespec/explicit.exp with GLIBC debuginfo installed, I run into: ... (gdb) break -source exp^GlFAIL: gdb.linespec/explicit.exp: complete \ non-unique file name (timeout) ... The regexp that times out is: ... -re "break -source exp\\\x07licit" { ... and the reason it times out is that gdb only outputs an "l" after the tab, while the regexp expect a futher "icit". This is a regression since commit 507dd60e28 "[gdb/testsuite, 1/2] Fix gdb.linespec/explicit.exp with check-read1", where I merged the matching for the two cases where GLIBC debuginfo is either installed or not, as it turns out incorrectly, presumably because even though I tested with GLIBC debuginfo info installed and deinstalled, that didn't make a difference because I didn't use configure flag --with-separate-debug-dir=/usr/lib/debug. Fix this by not explictly matching the "icit" part. Tested on x86_64-linux, with and without GLIBC debuginfo installed, both with make targets check and check-read1. gdb/testsuite/ChangeLog: 2020-03-12 Tom de Vries <tdevries@suse.de> * gdb.linespec/explicit.exp: Fix "complete non-unique file name" test in presence of GLIBC debuginfo.
…
…
…
…
…
…
…
…
…
…
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.
Description
Languages
C
51.8%
Makefile
22.4%
Assembly
12.3%
C++
6%
Roff
1.4%
Other
5.4%