mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-06-26 05:47:26 +08:00
5897fd4994
GDB silently ignores attempts to enable branch tracing on a thread that is already recorded. This shouldn't happen as recording is enabled exactly once: - when the btrace record target is opened for existing threads - when a new thread is added while the btrace record target is pushed GDB also silently ignores if recording is disabled on threads that were not recorded. This shouldn't happen, either, since when stopping recording, we only disable recording on threads that were recorded. GDB further silently ignores if recording was not enabled by the corresponding target method. Also this shouldn't happen since the target is supposed to already throw an error if recording cannot be enabled. This new error in btrace_enable catches cases where the target silently failed to enable recording. Throw an error in those cases. This allows us to detect an actual issue more easily. It will be addressed in the next patch. gdb/ChangeLog: 2020-03-19 Markus Metzger <markus.t.metzger@intel.com> * btrace.c (btrace_enable): Throw an error on double enables and when enabling recording fails. (btrace_disable): Throw an error if the thread is not recorded.
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.