public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Bossom, John" <John.Bossom@Cognos.COM>
To: "'beckmann.bremen@t-online.de'" <beckmann.bremen@t-online.de>,
	 pthreads-win32@sources.redhat.com
Subject: RE: pthread_key_create destructor
Date: Mon, 06 Jan 2003 14:48:00 -0000	[thread overview]
Message-ID: <BF85C64585F2D61190EF0002A5CE6F346C9028@sottexch2.cognos.com> (raw)

Note:

You need to call pthread_exit() in your example... you should
be able to find documentation in several books that indicate
that you need to do this to ensure the key destructors are
called on the main thread of execution
(i.e. this is not a pthread-win32 specific thing)

Cheers,
John

-----Original Message-----
From: beckmann.bremen@t-online.de [mailto:beckmann.bremen@t-online.de]
Sent: Friday, January 03, 2003 10:30 AM
To: pthreads-win32@sources.redhat.com
Subject: pthread_key_create destructor


Hi,

I have a problem with pthread_key_create ().
I'm using the latest(2002-11-4) pre-build pthreadVC.dll on Windows XP with 
MSVC++ 6.0.
I wrote the following example to explain the problem:

#include <pthread.h>
#include <windows.h>
#include <stdio.h>

pthread_key_t key;

void destructor (void *ptr)
{
	printf ((char*)ptr);
	free (ptr);
}

int main (int argc, char *argv[])
{
	char *ptr;

	pthread_key_create (&key, &destructor);
	if ((ptr = pthread_getspecific(key)) == NULL) {
		ptr = strdup ("test\n");
		pthread_setspecific (key, ptr);
	}
	return 0;
}

I think, this is a valid example, and it works fine as a release version 
but the debug version crashes inside the destructor() function .
The address of ptr inside destructor() is the same as inside main() but 
when having a look at the memory pointed to by ptr, it is initialized to 
zero at the end of main but unspecified inside of destructor().
It seems, that the address of ptr is already outside the applications 
address space or somehow else invalid, so the destructor is called too late.


Thanks for any help,

Thomas Beckmann

This message may contain privileged and/or confidential information.  If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.  Thank you.

             reply	other threads:[~2003-01-06 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-06 14:48 Bossom, John [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-03 15:30 Thomas Beckmann

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=BF85C64585F2D61190EF0002A5CE6F346C9028@sottexch2.cognos.com \
    --to=john.bossom@cognos.com \
    --cc=beckmann.bremen@t-online.de \
    --cc=pthreads-win32@sources.redhat.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).