From: "Alexey Sushkov" <sushkov@dins.ru>
To: <pthreads-win32@sourceware.cygnus.com>
Cc: "'Phil Frisbie, Jr.'" <phil@hawksoft.com>
Subject: RE: Posix
Date: Mon, 04 Jun 2001 01:26:00 -0000 [thread overview]
Message-ID: <001d01c0ecd8$86f88960$34bd77d4@alex2000> (raw)
In-Reply-To: <3B17C9EF.F52BB5AB@hawksoft.com>
Hello Phil,
I've got it.
Yes, I had problems with running some app. The app is crashed inside POSIX
Threads for Win32 Library. After I allocate memory before calling xxx_init
functions the problem is disappeared. Now I understand that the problem not
in using POSIX function but the memory is corrupted somewhere else.
Thank you,
Alexey Sushkov.
-----Original Message-----
From: Phil Frisbie, Jr. [ mailto:phil@hawksoft.com ]
Sent: Friday, June 01, 2001 7:59 PM
To: Alexey Sushkov
Subject: Re: Posix
Alexey Sushkov wrote:
>
> Hello Phil,
>
> Thank you for quick answer. Yes I'am using POSIX Threads for Win32
Library.
Sorry for that question, I did not notice that your message came from the
pthreads-win32 mail list. Did I reply to the list, or directly to you? I was
not
yet fully awake this morning :)
> I have new question: are you allocate memory before using the functions?
No. Both pthread_attr_init and pthread_mutex_init allocate the structures.
> If yes it means that the app I am porting has bugs because there no memory
> allocation before using the functions. There is passed only a pointer to
> pointer into the functions.
You only pass a pointer to pointer for both.
Are you having a problem compiling your app? Or running it?
> With best regards,
> Alexey Sushkov.
Phil Frisbie, Jr.
Lead Developer, Hawk Software
http://www.hawksoft.com
next parent reply other threads:[~2001-06-04 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B17C9EF.F52BB5AB@hawksoft.com>
2001-06-04 1:26 ` Alexey Sushkov [this message]
2001-06-01 7:03 Posix Bossom, John
-- strict thread matches above, loose matches on Subject: below --
2001-06-01 5:43 Posix Alexey Sushkov
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='001d01c0ecd8$86f88960$34bd77d4@alex2000' \
--to=sushkov@dins.ru \
--cc=phil@hawksoft.com \
--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).