🚀 go-pugleaf

I regularly debug through a huge shared library with gdb.  Occasionally
gdb will do odd things like:

  Sometimes it will allow me to place a breakpoint, then never break at
  the location I specified.

  Sometimes when I hit a breakpoint or an abort statement, it will show
  the current program counter at the last line of the file that it's in.

These two events occur on a Sparc, running 4.1.1.  The entire library is
compiled with gcc 2.3.2.  It is possible that this is a known bug.  If it
is, then add my name to those who request it fixed.  If it is NOT a known
bug, I can supply the appropriate shared libraries and executables to make
it happen.  Be warned, the shared library is 3.6MB (including debugging
information).

Unfortunately, this bug has not lent itself to creating a small sample
program...it happens infrequently, and when we rebuild, it sometimes
disappears!

When I have built and linked the library statically, it works.  However,
if you've ever tried building a 3.6MB library (takes a few minutes on a
sparc 2), you probably know that debugging through a shared library is 
much quicker.

Let me know how I should proceed.
-- 
____
\  /Dan Greening    Software Transformation   1601 Saratoga-Sunnyvale Rd, #100
 \/dgreen@sti.com   (408) 973-8081 x313       Cupertino, CA 95014