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:content-transfer-encoding
	:mime-version; q=dns; s=default; b=XDw08MZyF1caigesGIa0zXdlS9enz
	a077uOAk2Eq+ua3yNtDr1wWzzj4IMP1ZDDvgodcmAMny1zKNqI/FFadAFd0jMJm5
	HTbjfrn7ZnPPrdZEQNsvcCA979v5TlE78zqODW9zAyhFBrXBBd6X1mgPEKp9QtZo
	c2vPUGJgeggjno=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Jay P. Elston" <jay.elston@oemgroupinc.com>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>,
        The Cygwin Mailing List	<cygwin@cygwin.com>
Subject: RE: How can I determine why gdb throws unknown exceptions when debugging programs with threads on my Cygwin installation?
Date: Sat, 26 Oct 2019 02:34:12 +0000
Message-ID: <84846bf94ea446ca9e2cab4935c6eebb@OEM26.oemsurplus.local>
References: <b0f98e400a8e4787b3e8b0b14a7a9baa@OEM26.oemsurplus.local> <b4be0a80-b158-3278-6610-74f59b03cfa2@dronecode.org.uk> <0F7D3B1B3C4B894D824F5B822E3E5A178FDF90A8@IRSMSX102.ger.corp.intel.com>
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A178FDF90A8@IRSMSX102.ger.corp.intel.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

On October 25, 2019 6:48 AM, Michael Soegtrop wrote:

>It has been reported in the past that antivirus software from Trend Micro result in STATUS_GUARD_PAGE_VIOLATION in ntdll!RtlAllocateHeap ().

>See: http://cygwin.1069669.n5.nabble.com/XWin-startup-crash-x86-64-Windows-10-td126544.html#a126561

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:

Thread 7 received signal ?, Unknown signal.
[Switching to Thread 8736.0x2bf4]
0x0000000077947b97 in ntdll!RtlAllocateHeap ()
   from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
(gdb) bt f
#0  0x0000000077947b97 in ntdll!RtlAllocateHeap ()
   from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
No symbol table info available.
#1  0x00000000779f233d in ntdll!EtwEventWriteStartScenario ()
   from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
No symbol table info available.
#2  0x00000000779f3014 in ntdll!EtwEventWriteStartScenario ()
   from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
No symbol table info available.
#3  0x0000000077947b9c in ntdll!RtlAllocateHeap ()
   from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
No symbol table info available.
#4  0x000007fefd2e1c68 in TmmonDestoryAddonObject ()
   from /cygdrive/c/Windows/system32/tmumh/20019/AddOn/8.20.0.1028/TmUmEvt64.dll
No symbol table info available.
#5  0x000007fefd2267ab in ?? ()
   from /cygdrive/c/Windows/system32/tmumh/20019/AddOn/8.20.0.1028/TmUmEvt64.dll
No symbol table info available.
#6  0x000007fefd2a551a in TmmonDestoryAddonObject ()
   from /cygdrive/c/Windows/system32/tmumh/20019/AddOn/8.20.0.1028/TmUmEvt64.dll

This is not a Cygwin problem -- the solution is to be to add the Cygwin bin directory to Trend Micro's exception list. I will give this a try
after I get our IT department to do this.


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