🚀 go-pugleaf

Two problems on a Sparc-

1- gdb seems to be stupid wrt local procedure names, 
   (when the file aint compiled with -g)
   even though adb finds them handily

   Compare cases A) and B) below- adb found _tmpIOErrorHandler
   and __DYNAMIC, bug gdb used the previous global symbols)

2- if a shared library DOES exist, gdb doesn't seem to work.
   Note that this isn't the same sparc that the user used,
   but the executable is the same and the shared lib is identical
   (I copied it myself).
  
   This is shown in C) below.

3- Note that in all the gdb cases, gdb says as it starts up:
	Warning: core file may not match specified executable file.
   What criteria does it use to discern this?

Thanks- ras@frame.com

   With libc.so.1.6 missing I get:
A)   With gdb 4.5
       /usr/lib/libc.so.1.6: No such file or directory.
       (gdb) where
       #0  0xf775c120 in _mb_cur_max ()
       #1  0xf777447c in _mb_cur_max ()
       #2  0x2a9578 in WmInit ()
       ...

B)   With adb
       ?(?)
       __DYNAMIC(0x1,0x0,0x640e,0x640c,0x7,0x4e) at f775c120
       _tmpIOErrorHandler(0x464210,0x2a94b0,0x20488001,0x8...

   When libc.so.1.6 exists I get:
C)   With gdb 4.5
       #0  0xf775c120 in kill ()
       Cannot access memory at address 0xf775c118.

D)   With adb
       _kill(?)
       __DYNAMIC(0x1,0x0,0x640e,0x640c,0x7,0x4e) + 8
       _tmpIOErrorHandler(0x464210,0x2a94b0,0x20488001,0x8000000,0xf831...
       __XIOError(0x464210,0xf7ffecd0,0x0,0x432400,0x20,0x432400) + 28

-end-