From: Mike McCarty <mcmccarty@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Corrupt Cygwin64 install?
Date: Mon, 26 Sep 2016 21:09:00 -0000 [thread overview]
Message-ID: <CACt7iwkxqeKxYxjYp=G8SwbzXyPAqDbX1veM3pEMhy3XRtLqRw@mail.gmail.com> (raw)
In-Reply-To: <4d6d5c2c-f724-5a00-ba6c-fdf5ac220495@cornell.edu>
I finally got back to looking at this...
I reinstalled cygwin64 from scratch. Removed all of my .*rc files and
other customizations. No change.
So I decided to run it in the debugger:
$ gdb /usr/bin/emacs-nox.exe
(gdb) r
Starting program: /usr/bin/emacs-nox.exe
[New Thread 9896.0x2308]
[New Thread 9896.0x40c]
[New Thread 9896.0x2a8c]
[New Thread 9896.0x20f4]
[New Thread 9896.0x27bc]
[New Thread 9896.0x488]
[New Thread 9896.0x1ae0]
[Thread 9896.0x2a8c exited with code 0]
[New Thread 9896.0x2b54]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 9896.0x2b54]
0x000007fefcb07497 in TmmonDestoryAddonObject () from
/cygdrive/c/windows/system32/tmumh/20019/AddOn/6.80.0.1007/TmUmEvt64.dll
(gdb) where
#0 0x000007fefcb07497 in TmmonDestoryAddonObject () from
/cygdrive/c/windows/system32/tmumh/20019/AddOn/6.80.0.1007/TmUmEvt64.dll
#1 0x000007fefcae4a55 in ?? () from
/cygdrive/c/windows/system32/tmumh/20019/AddOn/6.80.0.1007/TmUmEvt64.dll
#2 0x000007fefcae3ffb in ?? () from
/cygdrive/c/windows/system32/tmumh/20019/AddOn/6.80.0.1007/TmUmEvt64.dll
#3 0x000007fefcae3b88 in ?? () from
/cygdrive/c/windows/system32/tmumh/20019/AddOn/6.80.0.1007/TmUmEvt64.dll
#4 0x000007fefcaea4d3 in ?? () from
/cygdrive/c/windows/system32/tmumh/20019/AddOn/6.80.0.1007/TmUmEvt64.dll
#5 0x000007fefcaf6b5a in ?? () from
/cygdrive/c/windows/system32/tmumh/20019/AddOn/6.80.0.1007/TmUmEvt64.dll
#6 0x00000000748960f6 in ?? () from
/cygdrive/c/windows/system32/tmumh/20019/TmMon/1.6.0.1163/tmmon64.dll
#7 0x0000000074933ac7 in tmmon64!NullExport () from
/cygdrive/c/windows/system32/tmumh/20019/TmMon/1.6.0.1163/tmmon64.dll
#8 0x00000000749337ca in tmmon64!NullExport () from
/cygdrive/c/windows/system32/tmumh/20019/TmMon/1.6.0.1163/tmmon64.dll
#9 0x00000000748972dd in ?? () from
/cygdrive/c/windows/system32/tmumh/20019/TmMon/1.6.0.1163/tmmon64.dll
#10 0x00000001800b2a84 in CreateMutexW () from /usr/bin/cygwin1.dll
#11 0x000000018004415b in init_cygheap::add_tls(_cygtls*) () from
/usr/bin/cygwin1.dll
#12 0x00000001800bd80c in pthread_wrapper () from /usr/bin/cygwin1.dll
#13 0x000000018004577b in _cygtls::call2(unsigned int (*)(void*,
void*), void*, void*) () from /usr/bin/cygwin1.dll
#14 0x00000001800457e4 in _cygtls::call(unsigned int (*)(void*,
void*), void*) () from /usr/bin/cygwin1.dll
#15 0x0000000076dc59bd in KERNEL32!BaseThreadInitThunk () from
/cygdrive/c/windows/system32/kernel32.dll
#16 0x0000000076efa2e1 in ntdll!RtlUserThreadStart () from
/cygdrive/c/windows/SYSTEM32/ntdll.dll
#17 0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
tmmon64.dll is a TrendMicro OfficeScan dll. After talking my sysadmin
into disabling OfficeScan on my machine temporarily, the crash goes
away. Adding cygwin to the exclusion list doesn't help here (I tried
it) I think because this is a "real-time monitor", not the file scan
that the exclusion list generally applies to.
Has anybody else had a similar experience with TrendMicro AV software?
My IT dept. will not allow me to disable it entirely...
--
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
next prev parent reply other threads:[~2016-09-26 20:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 22:35 Mike McCarty
2016-09-22 14:18 ` Ken Brown
2016-09-26 21:09 ` Mike McCarty [this message]
2016-09-27 2:00 ` Ken Brown
2016-09-27 2:18 ` Brian Inglis
2016-09-27 15:05 ` Mike McCarty
2016-09-27 17:59 ` Achim Gratz
2016-09-27 18:06 ` Mike McCarty
2016-09-27 18:12 ` Achim Gratz
2016-09-27 18:29 ` Achim Gratz
2016-09-27 20:15 ` Mike McCarty
2016-09-28 0:06 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2016-09-21 22:04 Mike McCarty
2016-09-21 22:09 ` Ken Brown
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='CACt7iwkxqeKxYxjYp=G8SwbzXyPAqDbX1veM3pEMhy3XRtLqRw@mail.gmail.com' \
--to=mcmccarty@gmail.com \
--cc=cygwin@cygwin.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).