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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=Hm0LlNz
	rlb523b/a3i1X7y2xvzP4L1/Gm9HvmlQswckBAgSiyqAfNCz7NnIviHW/YMW33vz
	g7Q7UUduK3fDGbabL7ExE7akAJlQ8Q0ivzX891Dtxd6t7O4nm3y/0CPN35Xdu5ao
	z7ZZudF8REQZnfj4uXFTJ9CIadqQzrsekqsU=
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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=rDSb1pZiP1zNQ
	JR1beSyqiwiKtM=; b=LM0yBY9J3wXBF8DDSd1TwsBUzqSvWO34S9EkCT7aW5efm
	MgekpQkTQd7fVX65QgVSHtj8Mk1rbsX2jFprbGd0N5lw2wtmZPaimj26mzqd+1n8
	75dfw57kcRVFVvkZn09ui/uNv5Jv0PZJy0pbMsfj7K44MkW3guYl5ruMBG/eGU=
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.2 required=5.0 tests=AWL,BAYES_20,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=D*org.uk, sk:jontur, U*jon.turney, sk:jon.tur
X-HELO: mail-oi0-f41.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to;        bh=4jjwI9ZQRTzWXIqFo+jB7GbPlQ3+0TbPRaD0PnXCIE4=;        b=kI73SN58qtublJ+HABEmBFJqDzGo80yk4yfS+2fhYZPzRvhy5FIzTu+SRw5LGhCCXx         6Z5vUnHZsrqTh95AVih+4WSR1yRp6QpJTdE0t1iFk9paYkUsgaFcXdc0aBaV62eUycpo         3AvQsKhW8S9Xyhwz6m9pp7Y/7VEVuOAofH4f7Jd8Y6t1X9oyst//Wpj/cDhdQlHCAuMn         Wxwxw9EA1cwd42ZyOJVd2r5qBIxHcOtBPQzmHradX2XZ10L5Exgz2a7l1tjwkI5BNNkp         L7snKETSQDZ6YoQ7MgYyH8ipND+PEO4ZjPeAGsTd49lrZqFqB6NDwpcy2hYescCzyBOd         B8tA==
X-Gm-Message-State: AE9vXwPJ8rS7Tjp+4JQAxFwS8DfJAVx3R3ZAG4VUDDMjIYbAV7epILGhPV7SA9imS+nWVXplTWOD21UhSHKcxw==
X-Received: by 10.157.43.87 with SMTP id f23mr18632699otd.83.1473660060616; Sun, 11 Sep 2016 23:01:00 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <48e78f73-875e-42db-f9a9-4d4d445799ed@dronecode.org.uk>
References: <CABo5xTrsEjGug4rZYmCsksK4NfHSqppuegtT6Gqtot+E+CpwRg AT mail DOT gmail DOT com> <48e78f73-875e-42db-f9a9-4d4d445799ed AT dronecode DOT org DOT uk>
From: Reto <rh03260503 AT gmail DOT com>
Date: Mon, 12 Sep 2016 08:01:00 +0200
Message-ID: <CABo5xToMVigwKq8rLPvyXL5sZH7a+o1d6DW57KHC=0hETRr4fA@mail.gmail.com>
Subject: Re: gdb : Exception in SetThreadName(unsigned long, char const*) () from /usr/bin/cygwin1.dll
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

Hi Jon

Thanks a lot for your valuable help. I did update gdb to version
7.11.1-1 test release. Now it works fine.

Have a nice day,
Reto

On Sat, Sep 10, 2016 at 1:39 PM, Jon Turney <jon DOT turney AT dronecode DOT org DOT uk> wrote:
> 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