once more into the breach - please try a snapshot so I can release this thing

[James R. Phillips]

Although a cygwin package maintainer, I am a complete novice at debugging
cygwin programs, so please bear with me.

The current cygwin1.dll snapshot (2006.01.12) causes octave (a package I
maintain) to dump core under some circumstances.  I haven't been able to
isolate just what causes it.  When this happens, I get the following error
message _on_exit_ :

===
octave:3> exit
Aborted (core dumped)
===

This causes octave to write an octave-core file, which apparently is not
something gdb understands, but is a binary file that octave can load to restart
a computation.  I take the core dump error message to have originated in
octave, rather than cygwin.

In order to further investigate this, I tried gdb, with the following results:

===
$ gdb -q /usr/bin/octave
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/octave.exe

Program received signal SIGSEGV, Segmentation fault.
0x610ae8d8 in pthread_key_create () from /usr/bin/cygwin1.dll
(gdb)
===

I interpret this to mean a segfault has occurred even prior to any
computations.  This surprises me because if I don't use gdb, I can apparently
load and exit octave, doing no computations between load and exit, without any
aborts, segfaults, or obvious error messages.

Advice on where to go from here in debugging the problem would be appreciated.

Jim Phillips
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cygcheck.txt
URL: <http://cygwin.com/pipermail/cygwin/attachments/20060113/3cfff8db/attachment.txt>
-------------- next part --------------
--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/