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:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=oT5XBvRo2NliFsTF
	aBN1X/BpPzGM7DsjthzvD3ltLiF4qfnIpxUIDZ7EGMkxUa8mMNvioS1uEmL4wLQm
	YPXh4Q8kQ5x6vh0N9NLSWIZEoor7KhGP7CMla04thpSEu9Ov4ajdA5wydGKHOLej
	bowVeQ3P3Jmtno0mMWWSxwTJAXM=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Subject: Re: 2.4-2.5 x64: bash crashes on backticks, gdb crashes on opening core dump
To: cygwin AT cygwin DOT com
References: <56EE67C4 DOT 1070900 AT mail DOT mipt DOT ru>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <56EE9BDF.4080101@gmail.com>
Date: Sun, 20 Mar 2016 13:47:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <56EE67C4.1070900@mail.mipt.ru>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

On 20/03/2016 10:05, Ivan Pozdeev wrote:
> bash
> ----
> I'm being plagued by these crashes for about half a month now.
> Specifically, it cannot run any `configure' script.
> The crashes appear to happen in child bash/sh processes launched while
> processing backticks. Other times, commands with stream redirection fail
> silently or produce nothing. Simple commands or very short scripts do
> not fail.

Any BLODA around ?

> On trying to open `sh.exe.core', gdb 1.10 crashes, too; gdb 1.9 says
> "get_core_register_section: Assertion `core_vec' failed" (see
> attachment). So I'm unable to diagnose bash's problem right now.
>
> At another machine with the same packages, bash does not fail, but gdb's
> problem stands. Already tried reinstalling all the packages `bash'
> depends on and itself to no effect.
>
> gdb
> ---
> I managed to debug the gdb session with VisualGDB (trial).
> It turns out, the root cause is that the /bin/sh executable is x64, but
> the core file `sh.exe.core' - of the same executable - has i386 format!
> (objdump: <...>sh.exe.core:     file format elf32-i386)

Are you sure about the 64 bit dumper ?
https://www.cygwin.com/cygwin-ug-net/dumper.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