X-Recipient: archive-cygwin@delorie.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:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=QJ4cDKK8AhpOgm1d
	L5LGCw6tudTkfG2h++5ZbJ4K+uW2ga1GPKH+7y+yp8OaRRWAgwnUjvMbBEemRxVe
	xNjsc32ivCBkE+n3bTdaPclZTz85sSxHW4soalJjsNAVtAdYWE86k1+jyeo8p+6g
	Y1wwyOSAQH9zEQbYxwSv60KJ86U=
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:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=WTt67esr2WQp+LDO3TAY1g
	VBkGo=; b=ax7ZRHJk4reRJoN9UoeiVO7170mse5yxIw13r76apqqeu9RDx2XVIi
	gbeovdidvaoPxHYjGoU/ts6Jeuj0knjzF0uGnVqA/t2uDWeUMXhJ+L5FrrGDqzLJ
	Cc3xt6UP7IJGVp1b0XllYQa/NbWAtr4lzDsiFP2AvbauLv9Oc66hU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=Hx-spam-relays-external:ESMTPA, HContent-Transfer-Encoding:8bit
X-HELO: out2-smtp.messagingengine.com
X-ME-Sender: <xms:O6XfWWFpou3EmeilfR1kd-JIHA9ra3zwWwcesIwYukEiGZ-W6fwIEg>
Subject: Re: gdb 7.11.1-2 started within emacs fails
To: The Cygwin Mailing List <cygwin@cygwin.com>
References: <d4a9e76c90c44c7cb0fa915a2589c0f6@vsrv060ex03.ssd.fsi.com> <207e93bf-8f7e-57a3-1abc-cc645c79020c@cornell.edu> <9bed0b67-2930-ee6b-8361-4bf4d9d7d542@dronecode.org.uk> <9fbef412-169a-48fd-362e-249e0b585481@cornell.edu>
From: Jon Turney <jon.turney@dronecode.org.uk>
Message-ID: <934635e9-edcd-9668-76e1-b237efc918ff@dronecode.org.uk>
Date: Thu, 12 Oct 2017 18:24:09 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <9fbef412-169a-48fd-362e-249e0b585481@cornell.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Note-from-DJ: This may be spam

On 11/10/2017 21:32, Ken Brown wrote:
> On 10/11/2017 3:44 PM, Jon Turney wrote:
>> On 27/09/2016 21:15, Ken Brown wrote:
>>> On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
>>>> Using program foo:
>>>>       program foo
>>>>       e = 1.0
>>>>       stop
>>>>       end
>>>>
>>>> $ /usr/bin/gfortran    -g foo.f -o foo
>>>>
>>>> Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version 
>>>> 3.18.9) of 2016-09-17
>>>>
>>>> Inside emacs I ran M-x gud-gdb and got
>>>> ... GNU gdb (GDB) (Cygwin 7.11.1-2) 7.11.1 ...
>>>> (gdb) b 1
>>>> Breakpoint 1 at 0x4011d6: file foo.f, line 1.
>>>> (gdb) r
>>>> Starting program: /cygdrive/c/Users/harryr/foo.exe
>>>> [New Thread 6296.0x22ac]
>>>> [New Thread 6296.0x24d4]
>>>> readline: readline_callback_read_char() called with no handler!
>>>> Debugger aborted (core dumped)
>>>>
>>>> Foo written in C++ also fails with the same message.
>>>> Running gdb foo in bash gives the expected result:
>>>> gdb stops at first executable line prompting for next gdb command.
>>>
>>> I can confirm that this happens also with gdb-7.11.1-1 but not 
>>> gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on 
>>> x86.)
>>>
>>> It also fails with M-x gdb instead of M-x gud-gdb, but with a 
>>> different error message:
>>>
>>>    Failed to resume program execution (ContinueDebugEvent failed, 
>>> error 87)
>>
>> These problem seem not longer occur due to upstream changes in gdb 7.12.
> 
> Everything seems fine on x86_64 and with M-x gud-gdb on x86.  But when I 
> run M-x gdb on x86 (even with no file), gdb crashes.

Thanks for testing.

It seems this issue is known [1], so I made a gdb 7.12.1-2 with the 
work-around from there applied, which seems to fix M-x gdb on x86.

[1] https://sourceware.org/bugzilla/show_bug.cgi?id=21078


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

