Tom Tromey 9698f71410 Remove uses of fprintf_symbol_filtered ...

I believe that many calls to fprintf_symbol_filtered are incorrect.
In particular, there are some that pass a symbol's print name, like:

  fprintf_symbol_filtered (gdb_stdout, sym->print_name (),
			   current_language->la_language, DMGL_ANSI);

fprintf_symbol_filtered uses the "demangle" global to decide whether
or not to demangle -- but print_name does this as well.  This can lead
to double-demangling.  Normally this could be innocuous, except I also
plan to change Ada demangling in a way that causes this to fail.

2021-08-02 10:48:29 -06:00

..

lib/gdb

…

py-all-events.def

…

py-arch.c

…

py-auto-load.c

…

py-block.c

…

py-bpevent.c

…

py-breakpoint.c

…

py-cmd.c

gdb: remove cmd_list_element::function::sfunc

2021-07-23 15:38:54 -04:00

py-continueevent.c

…

py-event-types.def

…

py-event.c

…

py-event.h

…

py-events.h

…

py-evtregistry.c

…

py-evts.c

…

py-exitedevent.c

…

py-finishbreakpoint.c

…

py-frame.c

…

py-framefilter.c

Remove uses of fprintf_symbol_filtered

2021-08-02 10:48:29 -06:00

py-function.c

…

py-gdb-readline.c

…

py-inferior.c

…

py-infevents.c

…

py-infthread.c

…

py-instruction.c

…

py-instruction.h

…

py-lazy-string.c

…

py-linetable.c

…

py-newobjfileevent.c

…

py-objfile.c

…

py-param.c

…

py-prettyprint.c

…

py-progspace.c

…

py-record-btrace.c

…

py-record-btrace.h

…

py-record-full.c

…

py-record-full.h

…

py-record.c

…

py-record.h

…

py-ref.h

…

py-registers.c

…

py-signalevent.c

…

py-stopevent.c

…

py-stopevent.h

…

py-symbol.c

…

py-symtab.c

…

py-threadevent.c

…

py-tui.c

…

py-type.c

…

py-unwind.c

…

py-utils.c

…

py-value.c

…

py-varobj.c

…

py-xmethods.c

…

python-config.py

…

python-internal.h

…

python.c

…

python.h

…