mirror of
https://github.com/espressif/binutils-gdb.git
synced 2025-06-27 06:17:47 +08:00
bda9cb723c
* thread-db.c: Various comment fixes and additions. Include "bfd.h", "symfile.h" and "objfiles.h". (keep_thread_db): New variable. (find_new_threads_callback): Remove prototype. (thread_db_find_new_threads): New prototype. (thread_db_push_target, thread_db_unpush_target): Remove functions. (deactivate_target): New function. (thread_db_new_objfile): If OBJFILE == NULL, force deactivation of target vector. Activate target vector directly instead of calling thread_db_push_target. Set keep_thread_db if thread library is detected in the main symbol file. Only enable thread event reporting if there actually is a child process. Likewise for detecting new threads, done by calling thread_db_find_new_threads instead of iterating over the threads ourselves. (thread_db_detach): Call deactivate_target instead of thread_db_unpush_target. (thread_db_wait): Bail out early if we're not debugging the multi-threaded child process yet. (thread_db_post_startup_inferior): New function. (thread_db_mourn_inferior): Call deactivate_target instead of thread_db_unpush_target. (init_thread_db_ops): Add thread_db_post_startup_inferior to thread_db_ops.
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.