From: Mario Emmenlauer <mario@emmenlauer.de>
To: pthreads-win32@sourceware.org
Subject: crash with pthreads after dlclose()
Date: Mon, 07 Dec 2009 11:27:00 -0000 [thread overview]
Message-ID: <4B1CE678.7020306@emmenlauer.de> (raw)
Hi,
thank you for the pthreads-win32 project, its doing a great job
for us!
Currently we have an issue with a program crash on exit, which
seems to be related to pthreads. We are using FreeLibrary to close
a library, that uses pthreads internally. Since we do not call
pthreads directly, I don't know if I have to unregister/close/free
anything before calling FreeLibrary()?
The application crashes not at FreeLibrary(), but instead when it
exists normally.
Here is the top of the callstack, in case that helps:
pthreadVC2.dll!_ptw32_callUserDestroyRoutines() + 0xd8 bytes C
pthreadVC2.dll!_pthread_win32_thread_detach_np() + 0x2c bytes C
Thanks, and all the best,
Mario
--
Dipl. Inf. Mario Emmenlauer Office: +41-(0)44-430-1106
Bitplane AG Fax: +41-(0)44-430-1101
Badenerstrasse 682 mailto: mario * emmenlauer.de
CH-8048 Zurich http://www.marssoft.de / http://www.xuvtools.org
reply other threads:[~2009-12-07 11:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4B1CE678.7020306@emmenlauer.de \
--to=mario@emmenlauer.de \
--cc=pthreads-win32@sourceware.org \
/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).