X-Spam-Check-By: sourceware.org
Date: Fri, 13 Jan 2006 18:38:37 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: "James R. Phillips" <antiskid56-cygwin AT yahoo DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: once more into the breach - please try a snapshot so I canrelease  this thing
In-Reply-To: <20060113222525.72935.qmail@web51501.mail.yahoo.com>
Message-ID: <Pine.GSO.4.63.0601131835550.27020@access1.cims.nyu.edu>
References: <20060113222525 DOT 72935 DOT qmail AT web51501 DOT mail DOT yahoo DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-ID: 
Content-Disposition: INLINE
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Fri, 13 Jan 2006, James R. Phillips wrote:

> 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)

FWIW, you might want to download the cygwin1.dbg file associated with the
snapshot.  Assuming you save it in /tmp, at this point you'd issue the
command

(gdb) dll-symbols /tmp/cygwin1.dbg

to load the debugging symbols.  If you've already downloaded the .dbg
file, please ignore this.

> (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.

See <http://cygwin.com/ml/cygwin/2006-01/msg00464.html>.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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/