mirror of
https://github.com/bminor/binutils-gdb.git
synced 2025-11-16 12:34:43 +00:00
3de2dbe325
Ostensibly, the mdebugread.c is about reading debug information in the ecoff format, but it also supports stabs-in-ecoff according to comments in there, and also relied in some stabs facilities for ecoff reading itself. This commit takes the first step in removing stabs support by removing those dependencies from mdebug. And in order to support stabs-in-ecoff, mipsread would also call stabsread_new_init. Removing stabs-in-ecoff is trivial, as the code was well demarcated with comments mentioning where stabs was read. Plus the call to stabsread_new_init in mipsread can be trivially removed. Another simple removal was the dependence on stabs_end_psymtabs: because the local variables dependencies_used and includes_used were only touched by stabs-reading code, they are always 0 in the new version, which means we can find the exact code path that'd be followed in stabs_end_psymtab and move the relevant lines to mdebug instead. After all those, the last remaining dependency is when reading a fortran common block from an inferior compiled by SGI fortran compilers (and maybe more). The block could have no address, meaning it'd need to be fixed after all the minimal symbols have been read. This was done by adding the symbol to the stabs global_sym_chain, then calling scan_file_globals to fix them up. This commit copies all the necessary code for handling the fortran symbols onto mdebug, technically making some code duplication, but since stabsread will be removed soon, this shouldn't be too concerning. This change was tested in the compile farm's mips64 machine (number 230), where it actually seems to have solved some 50 failures in the testsuite, not including changes in tests from gdb.threads, as those are often very racy. I'm not sure if these were true fixes or racy cases, but since the new version has no newly introduced fails, only fewer of them, I'm inclined to think this change is at least harmless. Acked-By: Tom Tromey <tom@tromey.com>
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, and so on. 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.