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:cc:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=l2YiSsUTbOsxpmTA
	gOKJzLFaw/3R3KnzgqydfbeiLx5fsW9sTYIb9O0eXlywHvd2RPbfaKD0/wLkbLke
	qCRsgkYNxMxquvZjDlGHrtjjounumGcLmVsfw7Ks0zkMu78YKEI/0r8i0uJvV/Zf
	oSw20Co4HOe5AuDTzjrXAVVzZuw=
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:cc:reply-to:from
	:message-id:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=68WqYGPNUOZy2ifxUgB5Zf
	StO1E=; b=bBsNmt5LkHjos1Jtn6Pd+B1uR/LjzeAVz7ede6Q/5qPXKivQCH8FJJ
	J8ycbbtnbXfvw8DtE9JqSWl1hiGRb6Sbxj/tFC2OZPuvteyFldGNNHo+Q6cSdDF+
	mJlQwzFtqDjfpwO6JnHG3+Myq4O5bD++7NkiO9x26sHmqbagp2+F8=
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.8 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=reto, SetThreadName, setthreadname, Reto
X-HELO:	out4-smtp.messagingengine.com
Subject:	Re: gdb : Exception in SetThreadName(unsigned long, char const*) () from /usr/bin/cygwin1.dll
To:	cygwin AT cygwin DOT com
References:	<CABo5xTrsEjGug4rZYmCsksK4NfHSqppuegtT6Gqtot+E+CpwRg AT mail DOT gmail DOT com>
Cc:	Reto Huber <rh03260503 AT gmail DOT com>
Reply-To:	cygwin AT cygwin DOT com
From:	Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Message-ID:	<48e78f73-875e-42db-f9a9-4d4d445799ed@dronecode.org.uk>
Date:	Sat, 10 Sep 2016 12:39:48 +0100
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version:	1.0
In-Reply-To:	<CABo5xTrsEjGug4rZYmCsksK4NfHSqppuegtT6Gqtot+E+CpwRg@mail.gmail.com>

On 09/09/2016 05:15, Reto Huber wrote:
> I am using cygwin for quite a while. Yesterday I did update.
> Everything seemed to work smooth. Today I figured out that gdb does no
> longer work debugging my project. Even a simple "Hello World" can not
> be debugged anymore. The executable itself runs ok. Here the example

Thanks for reporting this problem, and the test case.

> gdb: unknown target exception 0x406d1388 at 0x7639c54f
>
> Program received signal ?, Unknown signal.

This is related to the thread name support added in 2.6.0

The exception used to pass the thread name to the debugger is supposed 
to be caught internally if the debugger doesn't handle it, but this 
doesn't seem to be working correctly on x86.

> Can you give me a hint how I can fix it? Can anyone reproduce the issue?

At the moment, the workaround would be to downgrade to Cygwin 2.5.2, or 
to update to the gdb 7.11.1-1 test release (which has explicit handling 
for these thread naming exceptions)


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