glitch in gdb-3.0/encore

Thread View: gnu.gdb.bug

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Dirk Grunwald Tue, 10 Jan 1989 16:50

#661

Author: Dirk Grunwald
Date: Tue, 10 Jan 1989 16:50

21 lines
1157 bytes

There appears to be a bug in GDB-3.0, that I've been unable to narrow
down, although I would beleive it's with the COFF code.

I have a set of subroutines (the ``zopen'' routines mentioned on the net
that read/write compress-format files) that use ``setjmp'' and ``longjmp''.

There's an error in the code that is raised after a longjmp occurs.

On the Encore/UMAX, GDB-3.0 reports the error as occuring in a routine
called `sv', which is related to the setjmp/longjmp code. It gives no line
numbers in the stack trace.

SDB on the other hand, shows the error as occuring at a specific line in
the routine, with a backtrace.

I can send the code to anyone wishing to tackle this.

Dirk Grunwald
Univ. of Illinois
grunwald@m.cs.uiuc.edu

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads