[143] in Pthreads mailing list archive
Re: pthreads with guile?
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Sat Oct 14 22:16:21 1995
Date: Sat, 14 Oct 1995 21:59:55 -0400
From: Ken Raeburn <raeburn@cygnus.com>
To: sudhir halbhavi <halbhavi@eecs.ukans.edu>
Cc: grib@cs.utexas.edu, pthreads@MIT.EDU
In-Reply-To: sudhir halbhavi's message of Sat, 14 Oct 1995 16:50:46 -0500
(CDT)
From: sudhir halbhavi <halbhavi@eecs.ukans.edu>
Date: Sat, 14 Oct 1995 16:50:46 -0500 (CDT)
> #2 0xbffff4e0 in end ()
I get these end () functions during backtraces, but haven't been able
to figure out what it is. Any info appreciated.
In many configurations, the linker adds a symbol "end" after the last
byte of allocated bss storage. So if the PC in a given frame is at
some high address (as happens when dealing with signals), that's the
best guess that the debugger can make. On some systems I've seen it
print a message like "Signal N received" or something.