FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* xcoffread.c (read_xcoff_symtab): Fix obsolete comment about

Browse source 
mst_solib_trampoline.

	* f-valprint.c (f_val_print): Change cast of valaddr from
	CORE_ADDR * to char **, since that is how it is used.

	* dbxread.c (read_dbx_dynamic_symtab): Save copy of symbol names
	using obsavestring, and pass that to prim_record_minimal_symbol.
	Having the objfile point to bfd_asymbol_name directly doesn't work
	if we save and restore a mapped symbol file.
This commit is contained in:
Jim Kingdon 1994-09-14 22:45:49 +00:00
parent 809ee7e036
commit f69ecb9c9a
4 changed files with 40 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

11
gdb/xcoffread.c
View file

@ -1373,9 +1373,12 @@ function_entry_point:
breakpoints, using malloc, etc). On the other side, this is
consistient with gdb's behaviour on a SUN platform. */
/* Trying to prefer *real* function entry over its trampoline,
by assigning `mst_solib_trampoline' type to trampoline entries
fails. Gdb treats those entries as chars. FIXME. */
/* FIXME: I think this code is using "<trampoline>" instead of
the real name because there didn't used to be a way to prefer
mst_text symbols over mst_solib_trampoline symbols (in fact,
it was using mst_unknown because mst_solib_trampoline didn't
exist yet). Using the real name would cause better output
from print_address. */
/* Recording this entry is necessary. Single stepping relies on
this vector to get an idea about function address boundaries. */
@ -1386,7 +1389,7 @@ function_entry_point:
#else
/* record trampoline code entries as mst_solib_trampoline symbol.
When we lookup mst symbols, we will choose mst_text over
When we lookup minimal symbols, we will choose mst_text over
mst_solib_trampoline. */
RECORD_MINIMAL_SYMBOL (cs->c_name, cs->c_value,