public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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:00 -0000	[thread overview]
Message-ID: <84846bf94ea446ca9e2cab4935c6eebb@OEM26.oemsurplus.local> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A178FDF90A8@IRSMSX102.ger.corp.intel.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2087 bytes --]

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.

\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[ܝ\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB

  reply	other threads:[~2019-10-26  2:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 17:25 Jay P. Elston
2019-10-25 13:32 ` Jon Turney
2019-10-25 13:49   ` Soegtrop, Michael
2019-10-26  2:34     ` Jay P. Elston [this message]
2019-10-26  3:20       ` Brian Inglis
2019-10-28  8:40       ` Soegtrop, Michael

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84846bf94ea446ca9e2cab4935c6eebb@OEM26.oemsurplus.local \
    --to=jay.elston@oemgroupinc.com \
    --cc=cygwin@cygwin.com \
    --cc=michael.soegtrop@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).