From: jens.ohlund@secrc.abb.se
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Threads and Handles
Date: Tue, 04 Jul 2000 08:21:00 -0000 [thread overview]
Message-ID: <OF23447DBA.F147367C-ONC1256912.00544A2B@secrc.abb.se> (raw)
Hi !
I have declared a cyg_handle_t, a cyg_thread and a stack as static.
This thread I start and delete every now and then. In betwen, do I have to do something with the handle ?
Or the memory as well (I'm using the same stack the next time I create the thread).
I mean, the cyg_thread_create sets the cyg_handle_t, but what does it do with the handle if the handle already have some old
values ?
My problem is that after a certain time of create and delete this thread i get a SIGTRAP. And i can't understand why,
because I'm very careful to check that the thread have left OR is in last line of code in the thread method before I delete it.
Just to be sure that resources get back, and by resources I mean memory.
yours
Jens Ohlund
next reply other threads:[~2000-07-04 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-04 8:21 jens.ohlund [this message]
2000-07-04 8:37 ` Jonathan Larmour
2000-07-04 23:04 jens.ohlund
2000-07-12 17:19 ` Jonathan Larmour
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=OF23447DBA.F147367C-ONC1256912.00544A2B@secrc.abb.se \
--to=jens.ohlund@secrc.abb.se \
--cc=ecos-discuss@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).