Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!GINGER.BERKELEY.EDU!mcgrath%paris.Berkeley.EDU
From: mcgrath%paris.Berkeley.EDU@GINGER.BERKELEY.EDU (Roland McGrath)
Newsgroups: gnu.gdb.bug
Subject: GDB 3.1.1 bugs
Message-ID: <8905080137.AA06564@paris.Berkeley.EDU>
Date: 8 May 89 01:37:03 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 18

GDB 3.1.1 doesn't grok `long int', `unsigned int', etc.
(It takes only `long', `unsigned', `short', etc.)

Since `unsigned', `short', and `long', are type-modifiers,
not types, GDB should certainly accept their use in that capacity.

Also, GDB 3.1.1 treats unknown externals as type `char'.
For example, "p errno" prints one byte of the 4 in the `int' value.
"p read" prints the first byte in the code of the `read' function.

I think these should be treated as addresses of unknown type:

(gdb) p errno
{unknown} 0x2525

similar to
(gdb) p foo_func
{int ()} 0x5252