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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: gdb : Exception in SetThreadName(unsigned long, char const*) () from /usr/bin/cygwin1.dll
To: cygwin@cygwin.com
References: <CABo5xTrsEjGug4rZYmCsksK4NfHSqppuegtT6Gqtot+E+CpwRg@mail.gmail.com>
Cc: Reto Huber <rh03260503@gmail.com>
Reply-To: cygwin@cygwin.com
From: Jon Turney <jon.turney@dronecode.org.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>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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