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:subject:to:references:from:cc:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=xOoO+L3gKKeJUj88
	CIyNw8l4zHQw+yB/FT/zoy/bqfmz+nyjIqG7TnM/4ncZOM5+cZl78cPM8xaC6LMr
	eb+T9TX2r04RfEH5oXfbDIznepLlNZup1Rwrs8VVf556xUHOQ/T4RKObpOOdOgTm
	+1+d1WpnVEO2y3bZSdSLtsXSvGo=
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:subject:to:references:from:cc:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=V9vRkeNKkKx0ZDh/z6cCnH
	02pWw=; b=d8c+keggioNYspfbOV/3gjfAitCQ6rCJxr9HnfLIF6r5kr31tEcPK2
	/Y40c3UcsvGl7mh1BdEHrqni3Cw7Y3B0MhxEy2KidjBk5LQB2ZmeWykBW/lP5gMU
	Un71a2pE/ZeaiJPIZb5aV3VwiFN0do1yaDiK9HMhpdkAW3L7kTPVM=
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-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FORGED_SPF_HELO,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=no version=3.3.1 spammy=H*F:D*org.uk, HX-Languages-Length:1612
X-HELO: sa-prd-fep-043.btinternet.com
Authentication-Results: btinternet.com;    auth=pass (PLAIN) smtp.auth=jonturney AT btinternet DOT com
X-OWM-Source-IP: 86.141.128.179 (GB)
X-OWM-Env-Sender: jonturney AT btinternet DOT com
X-VadeSecure-score: verdict=clean score=0/300, class=clean
Subject: Re: assert creates unusable core dump on current stable Cygwin release
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
References: <CALK-3mJyg6pox9a+ZNgGmspcxBFcgGJ3XymXAOOPP6_Z_tSUjQ AT mail DOT gmail DOT com> <2300fe24-fc50-3d1c-6b1b-bf6da6022d2e AT SystematicSw DOT ab DOT ca> <b8379f49-3e22-23c8-80d9-d18f45e10a42 AT dronecode DOT org DOT uk> <71be3508-b11e-4681-eac6-9d44845088c7 AT SystematicSw DOT ab DOT ca>
From: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Cc: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Message-ID: <1ac90af2-412d-345f-da40-8260ae527096@dronecode.org.uk>
Date: Thu, 10 Oct 2019 20:19:25 +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: <71be3508-b11e-4681-eac6-9d44845088c7@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 09/10/2019 22:28, Brian Inglis wrote:
> On 2019-10-09 11:10, Jon Turney wrote:
>> 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
> 
> Given that it's used elsewhere, is there more to it than just:

Not sure what you are referring to by 'it', don't know where you mean by 
'elsewhere'.

> int
> dumper::init_core_dump ()
> {
>    bfd_init ();
> 
> - core_bfd = bfd_openw (file_name, "elf32-i386");
> + core_bfd = bfd_openw (file_name, "elf64-x86");

idk, have you tried it?

If I recall correctly, there's some code in gdb to handle these strange 
"'core dump'" files, which might well also need some attention for the 
x86_64 case.

(and I guess this patch is not acceptable as-is, as it looks like it 
would break x86)

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