From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79394 invoked by alias); 10 Sep 2016 11:40:08 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 79371 invoked by uid 89); 10 Sep 2016 11:40:08 -0000 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 Received: from out4-smtp.messagingengine.com (HELO out4-smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 10 Sep 2016 11:39:58 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2CE53204BC; Sat, 10 Sep 2016 07:39:56 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute5.internal (MEProxy); Sat, 10 Sep 2016 07:39:56 -0400 Received: from [192.168.1.102] (host86-141-129-68.range86-141.btcentralplus.com [86.141.129.68]) by mail.messagingengine.com (Postfix) with ESMTPA id B3064CCDB8; Sat, 10 Sep 2016 07:39:55 -0400 (EDT) Subject: Re: gdb : Exception in SetThreadName(unsigned long, char const*) () from /usr/bin/cygwin1.dll To: cygwin@cygwin.com References: Cc: Reto Huber Reply-To: cygwin@cygwin.com From: Jon Turney Message-ID: <48e78f73-875e-42db-f9a9-4d4d445799ed@dronecode.org.uk> Date: Sat, 10 Sep 2016 11:40:00 -0000 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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2016-09/txt/msg00160.txt.bz2 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