🚀 go-pugleaf

Sorry, it's not a bug report actually.

On Mon, 21 Feb 2005 05:21:59 -0500
Richard Stallman wrote:
 
> >     Also, run-time debugging log with dbx (gdb won't work),
> > manually newlined:
> 
> Why won't GDB work?  Have you tried installing the latest GDB?
> If that still fails, maybe it is a GDB bug--would you please
> report the GDB bug?

On the 5.3, it stalls with 'warning: Signal ? does not exist on
this system.', latest GDB 6.3 warns 'warning: wrong size gregset
struct in core file' when I debugged with core and if it's used
in the run-time debugging,

$ gdb ./bootstrap-emacs 
GNU gdb 6.3
[...]
This GDB was configured as "mips-sgi-irix6.5"...
DISPLAY = :0.0
TERM = kterm
Breakpoint 1 at 0x10108ab4
Breakpoint 2 at 0x100dd850
(gdb) run -q
Starting program: /opt/src/i18n/emacs/src/bootstrap-emacs -q

Program received signal SIGSEGV, Segmentation fault.
0x101a622c in ?? ()
(gdb) bt
#0  0x101a622c in ?? ()
#1  0x101a6504 in ?? ()
#2  0x101a952c in ?? ()
#3  0x101a9b50 in ?? ()
#4  0x101a9cd4 in ?? ()
#5  0x1018e628 in ?? ()
#6  0x1018ddd8 in ?? ()
#7  0x10394200 in ?? ()
warning: GDB can't find the start of the function at 0x10394200.

    GDB is unable to find the start of the function at 0x10394200
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
    This problem is most likely caused by an invalid program counter or
stack pointer.
    However, if you think GDB should simply search farther back
from 0x10394200 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
Previous frame inner to this frame (corrupt stack?)

This GDB 6.3 was compiled with GCC 3.4.3 with -O2 -W -Wall
-Wformat=2 -g without specific configure option. Also Emacs CVS-HEAD
done with same CFLAGS. If you'd think this is a bug or something
wrong, could you tell me, I'm wiling to submit a report (I have a
test log gdb.sum).

Regards,
-- 
Daichi