Toolchain/binutils-gdb
1
0
Fork 0
forked from Imagelibrary/binutils-gdb
Code Pull Requests Activity

* expprint.c (print_subexp): Add missing ']'.

Browse Source 
* defs.h (reg_names):  Fix declaration to match that in infcmd.c
	* stack.c (reg_names):  Delete redundant (and inconsistent) decl.
	* WHATS.NEW:  Point out improved C++ function name handling.
	* gdbtypes.c (lookup_fundamental_type):  For now, use the same
	type names for both implicitly and explicitly signed integral
	types.  See comment in the source code.
This commit is contained in:
Fred Fish
1992-06-12 20:51:42 +00:00
parent 28de880c48
commit 6b53bf346d
3 changed files with 38 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
gdb/ChangeLog
View File

@@ -1,3 +1,13 @@
Fri Jun 12 12:49:43 1992 Fred Fish (fnf@cygnus.com)
* expprint.c (print_subexp): Add missing ']'.
* defs.h (reg_names): Fix declaration to match that in infcmd.c
* stack.c (reg_names): Delete redundant (and inconsistent) decl.
* WHATS.NEW: Point out improved C++ function name handling.
* gdbtypes.c (lookup_fundamental_type): For now, use the same
type names for both implicitly and explicitly signed integral
types. See comment in the source code.
Thu Jun 11 12:31:50 1992 John Gilmore (gnu at cygnus.com)
Two `long long' fixes from Robert R. Henry (rrh@dino.tera.com):

10
gdb/WHATS.NEW
View File

@@ -1,6 +1,16 @@
What has changed since GDB-3.5?
(Organized release by release)
*** Changes in GDB-4.6:
* Better support for C++ function names
GDB now accepts as input the "demangled form" of C++ overloaded function
names and member function names, and can do command completion on such names
(using TAB, TAB-TAB, and ESC-?). The names have to be quoted with a pair of
single quotes. Examples are 'func (int, long)' and 'obj::operator==(obj&)'.
Make use of command completion, it is your friend.
*** Changes in GDB-4.5:
* New machines supported (host and target)

22
gdb/gdbtypes.c
View File

@@ -880,7 +880,21 @@ init_type (code, length, flags, name, objfile)
define fundamental types.
For the formats which don't provide fundamental types, gdb can create
such types, using defaults reasonable for the current target machine. */
such types, using defaults reasonable for the current target machine.
FIXME: Some compilers distinguish explicitly signed integral types
(signed short, signed int, signed long) from "regular" integral types
(short, int, long) in the debugging information. There is some dis-
agreement as to how useful this feature is. In particular, gcc does
not support this. Also, only some debugging formats allow the
distinction to be passed on to a debugger. For now, we always just
use "short", "int", or "long" as the type name, for both the implicit
and explicitly signed types. This also makes life easier for the
gdb test suite since we don't have to account for the differences
in output depending upon what the compiler and debugging format
support. We will probably have to re-examine the issue when gdb
starts taking it's fundamental type information directly from the
debugging information supplied by the compiler. fnf@cygnus.com */
struct type *
lookup_fundamental_type (objfile, typeid)
@@ -959,7 +973,7 @@ lookup_fundamental_type (objfile, typeid)
type = init_type (TYPE_CODE_INT,
TARGET_SHORT_BIT / TARGET_CHAR_BIT,
TYPE_FLAG_SIGNED,
"signed short", objfile);
"short", objfile); /* FIXME -fnf */
break;
case FT_UNSIGNED_SHORT:
type = init_type (TYPE_CODE_INT,
@@ -977,7 +991,7 @@ lookup_fundamental_type (objfile, typeid)
type = init_type (TYPE_CODE_INT,
TARGET_INT_BIT / TARGET_CHAR_BIT,
TYPE_FLAG_SIGNED,
"signed int", objfile);
"int", objfile); /* FIXME -fnf */
break;
case FT_UNSIGNED_INTEGER:
type = init_type (TYPE_CODE_INT,
@@ -1001,7 +1015,7 @@ lookup_fundamental_type (objfile, typeid)
type = init_type (TYPE_CODE_INT,
TARGET_LONG_BIT / TARGET_CHAR_BIT,
TYPE_FLAG_SIGNED,
"signed long", objfile);
"long", objfile); /* FIXME -fnf */
break;
case FT_UNSIGNED_LONG:
type = init_type (TYPE_CODE_INT,