DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:cc:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=d3vkRuhoVaeGvX4y
	g6z85PRvQg1F4K24RRuFJz1VoVg4NwOpO9hHtUNdVQOyIiL00vXVXtthgUfWanZS
	Jakeb5SN48wAW9Q5d8BNccI2XXgaYlO/yi7R6lngfjz105B+HB1MS4wovfazu+lF
	WXpGiuUjkTu4R/M+39IxmK0YtCs=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: assert creates unusable core dump on current stable Cygwin release
To: The Cygwin Mailing List <cygwin@cygwin.com>
References: <CALK-3mJyg6pox9a+ZNgGmspcxBFcgGJ3XymXAOOPP6_Z_tSUjQ@mail.gmail.com> <2300fe24-fc50-3d1c-6b1b-bf6da6022d2e@SystematicSw.ab.ca>
Cc: Brian.Inglis@SystematicSw.ab.ca
From: Jon Turney <jon.turney@dronecode.org.uk>
Message-ID: <b8379f49-3e22-23c8-80d9-d18f45e10a42@dronecode.org.uk>
Date: Wed, 9 Oct 2019 18:10:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <2300fe24-fc50-3d1c-6b1b-bf6da6022d2e@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 09/10/2019 16:31, Brian Inglis wrote:
> On 2019-10-09 01:14, Biswapriyo Nath wrote:
>> * mintty version: mintty 3.0.6 (x86_64-pc-cygwin)
>> * cygwin version: 3.1.0-0.6
>> * code:
>>
>> #include <assert.h>
>>
>> int main() {
>>    int x = 1;
>>    assert(x == 0);
>> }
>>
>> * Expected result: The terminal should show this message which appers
>> in latest stable cygwin version.
>> assertion "x == 0" failed: file "test.c", line 6, function: main
>>
>> * Actual result: terminal only shows "Aborted (core dumped)".
> 
> I also get the core dump, which is un-gdb-able below, as is it's core dump, on
> *current stable* Cygwin 64 releases *AND* see the message!

As far as I'm aware, the core-dump tool 'dumper' has never been fixed 
for x86_64, so I wouldn't expect this to work. See [1].

[1] https://cygwin.com/ml/cygwin/2016-03/msg00464.html

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