🚀 go-pugleaf

The problem of seeing things happen at etext+XXXX occurs when gdb
doesn't have symbols for part of the address space where it finds the
program executing.  This is a shared library problem.  GDB compounds
the problem by claiming it will single-step to the end of the procedure
and then sometimes doing something different.

GDB-4.0 will have SunOS shared library support, courtesy of
Schaefer@asc.slb.com.  At the moment, this support is not pretty, but
it works better.  I hope to make it work better by GDB-4.0.

In the meantime, the easiest circumvention is to link programs statically
if you want to debug them with gdb (link with "cc -Bstatic" or "ld -Bstatic").
If you compile with gcc -g, it already does this.

	John