From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: "Jay P. Elston" <jay.elston@oemgroupinc.com>
Subject: Re: How can I determine why gdb throws unknown exceptions when debugging programs with threads on my Cygwin installation?
Date: Fri, 25 Oct 2019 13:32:00 -0000 [thread overview]
Message-ID: <b4be0a80-b158-3278-6610-74f59b03cfa2@dronecode.org.uk> (raw)
In-Reply-To: <b0f98e400a8e4787b3e8b0b14a7a9baa@OEM26.oemsurplus.local>
On 23/10/2019 18:25, Jay P. Elston wrote:
> Hi all,
>
> I developed a problem debugging threads on my Cygwin installed on a Window 7 PC -- gdb throws an unknown target exception when it gets to the pthread_crreate() call.
This seems to be saying that the exception isn't thrown when not run
under gdb?
> This problem seems localized to my PC (even after reinstalling Cygwin), and I am wondering what my next trouble shooting steps might be.
>
> Here are the relevant lines from the gdb session:
>
> $ gdb a.exe
> GNU gdb (GDB) (Cygwin 8.1.1-1) 8.1.1
> . . .
> This GDB was configured as "x86_64-pc-cygwin".
> . . .
> Reading symbols from a.exe...done.
> (gdb) run
> Starting program: /home/jay.elston/threadTest/a.exe [New Thread 12908.0xc38] [New Thread 12908.0x25b4] [New Thread 12908.0x182c] [New Thread 12908.0x2958] [New Thread 12908.0x2ce4] [New Thread 12908.0x2878] [New Thread 12908.0x3044]
> gdb: unknown target exception 0x80000001 at 0x778e7b97
0x80000001 is STATUS_GUARD_PAGE_VIOLATION
gdb reports this as 'unknown', as there's no unix signal this can be
mapped to (for example, STATUS_ACCESS_VIOLATION is mapped to SIGSEGV)
Firstly, I'd suggest you do a 'bt' here, and see if any third party DLLs
are in the call stack (e.g. AV products, etc.)
> Thread 7 received signal ?, Unknown signal.
> [Switching to Thread 12908.0x3044]
> 0x00000000778e7b97 in ntdll!RtlAllocateHeap ()
> from /cygdrive/c/Windows/SYSTEM32/ntdll.dll
> (gdb) c
> Continuing.
> [Thread 12908.0x182c exited with code 2147483649] [Thread 12908.0x25b4 exited with code 2147483649] [Thread 12908.0x2878 exited with code 2147483649] [Thread 12908.0x2958 exited with code 2147483649] [Thread 12908.0x2ce4 exited with code 2147483649] [Inferior 1 (process 12908) exited with code 020000000001]
>
Thanks for the simple test case.
Unfortunately, this doesn't reproduce for me.
--
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:[~2019-10-25 13:32 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 [this message]
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
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=b4be0a80-b158-3278-6610-74f59b03cfa2@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).