From: Marisa DeMeglio <marisa@dinf.ne.jp>
To: pthreads-win32@sources.redhat.com
Subject: pthreads disappearing
Date: Thu, 13 May 2004 05:13:00 -0000 [thread overview]
Message-ID: <20040513050049.87412.qmail@web60602.mail.yahoo.com> (raw)
Hi,
I'm new to pthreads. What I'm trying to do is have an
application with two parts:
a) main process
b) GUI thread (using GTK)
Periodically, the main process needs to interrupt
gtk_main (gtk's main loop) when there is new data
available from the server (well it's another local
process but referring to it as a server will probably
convey the point). The server will call
main_process_dll->receiveData(data). Then the main
process can interrupt gtk_main with a gsignal (which
is out of the scope of this list). Otherwise, the GUI
thread needs to keep running until explicitly killed.
So, what I am seeing at the moment is when I create a
pthread, it runs for a short while and then
disappears. Does this have to do with the stack size?
I am passing in NULL as the second parameter to
pthread_create(). Even when I run my test program
without using GTK (and instead use a while(1) loop), I
see the same behavior.
Any advice would be much appreciated.
Thanks!
Marisa
reply other threads:[~2004-05-13 5:13 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=20040513050049.87412.qmail@web60602.mail.yahoo.com \
--to=marisa@dinf.ne.jp \
--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).