well as for ELF and SOM. Unify the descriptions of ELF and SOM
as "stabs in sections" rather than just saying "ELF and SOM".
Also make that stuff apply to COFF.
versus functions without line numbers, also mention stepping into
them as well as "step" when you are in them. Tell the user how to
deal with the situation. Add comment about "debugging information".
(Summary, C): fix xrefs in newly contributed text.
(Threads): index entries, clarifications, example
(passim): minor typos fixed, phrasing improvements
* remote.texi (Bootstrapping): rephrase text on ^C and add index
entries; (Server): explain use of gdbserver w/real-time systems,
add example of conflicting TCP port; (MIPS Remote) break up
running text into table, highlighting commands, and add example.
(these probably crept w/minor changes in spacing when A4 stuff
updated recently); update copyright date consistently
* cygref.tex: bring up to date with refcard.tex
to picking which Bbss.bss symbol to use, and (because there seems to
be no good way of doing it) re-write some of the text to make it
sound like Bbss.bss isn't such a great idea after all (as currently
designed).
good results, say they have to use stabs. Specifically say cfront
doesn't work well.
(Summary): Merge in information on Modula-2, Pascal, and Chill from
the gdb README. Add xrefs to places where the support for the various
languages is described in detail.
Change all references to stdout/stderr to gdb_stdout/gdb_stderr.
Replace all calls to stdio output functions with calls to
corresponding _unfiltered functions (`fprintf_unfiltered')
Replaced calls to fopen for output to gdb_fopen.
Added sufficient goo to utils.c and defs.h to make the above work.
The net effect is that stdio output functions are only directly used
in utils.c. Elsewhere, the _unfiltered and _filtered functions and
GDB_FILE type are used.
In the near future, GDB_FILE will stop being equivalant to FILE.
The semantics of some commands has changed in a very subtle way:
called in the right context, they may cause new occurences of
prompt_for_continue() behavior. The testsuite doesn't notice anything
like this, though.
Please respect this change by not reintroducing stdio output
dependencies in the main body of gdb code. All output from commands
should go to a GDB_FILE.
Target-specific code can still use stdio directly to communicate with
targets.
