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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:mime-version
	:content-transfer-encoding; q=dns; s=default; b=hC1Q7kJ5sp3XFBeB
	gafvskAwmPR0gTO/eMAVquwOkEs1pFSp/wK6nm2D1vJ0eIVC/wVfCWWrBc7t4Eiw
	iKo6eqF+IOKHIon6ITLbT1g1K02JkhSD3CSj3jI+D2h/3jHYMSaaHgblL19ZQ8Q4
	26825vpzdVpKWLt16ulzQqvblMc=
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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:mime-version
	:content-transfer-encoding; s=default; bh=Ou8KGPDrhjTf2eoIyIMIRh
	zi0xc=; b=T8JF2SLpCZ9byPypFzwnyoSwAZ7LxSTPHNk6V236kDoZ6XhxE1vZ7n
	fPK+A8650AMwr8DdysS0xr7FwgQMnktX31bwyvysv4rUw+6uDpztBpF2FjCPqx/p
	f2Jf1r4XmUSI2EzCA/o6kEjGuu47XKC7H6391QLLRYKu1K1PH+X5I=
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-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_50,SPF_PASS autolearn=ham version=3.3.1 spammy=Micro, nicole, April, april
X-HELO: mga03.intel.com
From: "Soegtrop, Michael" <michael DOT soegtrop AT intel DOT com>
To: "Jay P. Elston" <jay DOT elston AT oemgroupinc DOT com>,
        The Cygwin Mailing List	<cygwin AT cygwin DOT com>
Subject: RE: How can I determine why gdb throws unknown exceptions when debugging programs with threads on my Cygwin installation?
Date: Mon, 28 Oct 2019 08:40:16 +0000
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A178FDFA56B@IRSMSX102.ger.corp.intel.com>
References: <b0f98e400a8e4787b3e8b0b14a7a9baa AT OEM26 DOT oemsurplus DOT local> <b4be0a80-b158-3278-6610-74f59b03cfa2 AT dronecode DOT org DOT uk> <0F7D3B1B3C4B894D824F5B822E3E5A178FDF90A8 AT IRSMSX102 DOT ger DOT corp DOT intel DOT com> <84846bf94ea446ca9e2cab4935c6eebb AT OEM26 DOT oemsurplus DOT local>
In-Reply-To: <84846bf94ea446ca9e2cab4935c6eebb@OEM26.oemsurplus.local>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id x9S8eut2015978

Dear Jay,

> On the advice of Jon Turney, I ran a "bt f" command after gdb caught the
> exception, and it appears that a Trend Micro dll  (TmUmEvt64.dll) is where the
> error occurs:

Since the message with a similar problem I posted is from April 2016, it would also make sense to report this to Trend Micro. Maybe they can manage to fix this bug before another 3 1/2 years are over.

Best regards,

Michael
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928

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