public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Todd Owen <towen@lucidcalm.dropbear.id.au>
To: pthreads-win32@sourceware.cygnus.com
Subject: invalid page fault when using LoadLibrary/FreeLibrary
Date: Sat, 06 Nov 1999 10:37:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.93.991107015732.14870B-100000@ramtops.lucidcalm> (raw)

hi,
for me, pthread.dll consistently causes an "invalid page fault in
kernel32.dll" when I load it "explicitly"...to be precise, loading (with
LoadLibrary) isn't a problem, it gives the error when I call FreeLibrary.
I guess that the dll's cleanup must be causing the error.

Implicit linkage of the dll has never given me this problem.  Here's a
program (console application) that gives me the error:


#include <windows.h>
int main() {
  HINSTANCE hinst;

  hinst = LoadLibrary("pthread");
  printf("hinst == %d\n", hinst);
  printf("press a key to keel over...\n");
  getch();

  FreeLibrary(hinst);
  return 0;
}


I compile with: mingw32 (gcc-2.95 release), with the MSVCRT add-on (not
  that the compiler should make much difference in this case).
PTHREAD.DLL: is the precompiled 1999-11-02 one (I tried an older one as
  well, with the same result).

Fascinatingly, if you have your own dll (mycode.dll) which implicitly
loads pthread.dll, and then do LoadLibrary/FreeLibrary on _this_ dll, the
same thing happens.

Sorry, but I have no idea how to fix the problem.  It's taken me long
enough to track it down this far.

Todd.


             reply	other threads:[~1999-11-06 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-06 10:37 Todd Owen [this message]
1999-11-09  5:29 Bossom, John
1999-11-09  6:17 ` Todd Owen

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=Pine.LNX.3.93.991107015732.14870B-100000@ramtops.lucidcalm \
    --to=towen@lucidcalm.dropbear.id.au \
    --cc=pthreads-win32@sourceware.cygnus.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).