From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: "Jay P. Elston" <jay.elston@oemgroupinc.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: Mon, 28 Oct 2019 08:40:00 -0000 [thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A178FDFA56B@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <84846bf94ea446ca9e2cab4935c6eebb@OEM26.oemsurplus.local>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 953 bytes --]
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
\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\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ØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
prev parent reply other threads:[~2019-10-28 8:40 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
2019-10-26 3:20 ` Brian Inglis
2019-10-28 8:40 ` Soegtrop, Michael [this message]
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=0F7D3B1B3C4B894D824F5B822E3E5A178FDFA56B@IRSMSX102.ger.corp.intel.com \
--to=michael.soegtrop@intel.com \
--cc=cygwin@cygwin.com \
--cc=jay.elston@oemgroupinc.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).