🚀 go-pugleaf

This is gdb 3.3, on a 386 machine running 386/ix 2.0.2, which translates
to system V release 3.2 for gdb's purposes, I think.

(1) config.gdb does not list the i386-sysv3.2 and i386gas-sysv3.2
options in its list of possible machine types.  Also, those two options
still use /dev/null as the opcode file, despite the comments to the
contrary.  Changing those to use m-i386.h, by anaalogy with he i386
setup, worked fine.

(2) gdb produces the following error message when it is in the stack
frame with main in it, in place of the argument list:
	Error reading memory address 0x<some number> I/O error (5).
A program that produced that error is:
main(){}
(and putting a breakpoint at main.)

(3) If I use `l' in the stack frame with main, I get the error message:
	_globals_: No such file or directory
I'm not sure if this happens only with very short programs, or all the
time.

karl@umb.edu