X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	q=dns; s=default; b=QsZFtGoOqVbHiS+xzjVTi4ubzKADZqzPtFUuNZxGnXY
	hL79SPvmFTQeHOOJ3qbULDVA8XkoEZLvUqQNzDFbOzQHHRP6tO1p1y2m8RU41x0H
	7XJFW8xOl603wvQs309Qq7j/i4QYdwFLwc+2XCHrMSHKXSaIImy3hfcoELs3B5vo
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:references:in-reply-to:subject:date
	:message-id:mime-version:content-type:content-transfer-encoding;
	s=default; bh=rH6pfSt+G1T338CQSOVieT32QoQ=; b=lIu0ssMYsNuY8LR6n
	vImyhk++2brgdp3EQ0c0K5Nq0cRYjF3Qjv+04oia1IJu2qfBhoQO7JP+3nGY3961
	poM/iwjBGkxX/aGQE9qG2LNFcWUDPr9f96hEFbCfaZBPbrR7PastzUZqDd90O/m2
	kMf8C0yJkhTPqzhKVzWEmGdX+0=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.5 required=5.0 tests=AWL,BAYES_50,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2
X-HELO:	mailout1.w1.samsung.com
From:	Pavel Fedin <p DOT fedin AT samsung DOT com>
To:	cygwin AT cygwin DOT com
References:	<007601cfc5ef$09e5bb60$1db13220$%fedin AT samsung DOT com> <20140901152634 DOT GA18880 AT calimero DOT vinschen DOT de>
In-reply-to:	<20140901152634.GA18880@calimero.vinschen.de>
Subject:	RE: [BUG] Nasty bug persists on x86-64
Date:	Tue, 02 Sep 2014 11:06:15 +0400
Message-id:	<002d01cfc67c$637d8ad0$2a78a070$%fedin@samsung.com>
MIME-version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id s8278BNV032387

 Hello Corinna!

> Try `bt' at this point.  Maybe the backtrace shows something of
> interest.

 You haven't read the message completely. 'bt' cannot help since there's no debug information for ntdll and gdb is unable to unwind the stack correctly.

> Apart from that, try the latest snapshot from
> https://cygwin.com/snapshots/  I converted the internal exception
> handling avoiding crashes from system functions to SEH.  Perhaps the
> above doesn't show up with it.

 I have installed the snapshot, and looks like it's now stable. However, this exception actually persists. I can tell you some more details. The actual malfunction happens when this exception fires twice in a row. I managed to catch this with strace a couple of times, but didn't save logs unfortunately.
 I want to try to bisect for the origin of this crash. Currently i know that it happens before main(). But is main() a real entry point ? I believe it's not. Can you tell me what is the real binary's entry point in Cygwin ?

 Yesterday in the evening i replied from home with some more information, but my reply got lost again :(


Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -