public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Anthony Tonizzo" <atonizzo@lycos.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Error on Cyg_Counter::add_alarm
Date: Mon, 24 May 2004 04:08:00 -0000	[thread overview]
Message-ID: <GKAIOKFEACFEEEAA@mailcity.com> (raw)

Matt:

>I had some problems with alarms several months ago in
>the FreeBSD stack, but I can't remember the details. 

Fortunately it turns out to have been a very simple
mistake. The stack space allocated for the process was
too small, and when the second task kicked in, it was
probably overwriting the stack of the first. I still wonder
how I got away with this for so long, but once it was
increased to a much bigger size all issues disappeared.

Which brings up an interesting subject, which I am sure
can be of interest to many, especially those working in
somewhat "restricted spaces":

How do you estimate the amount of stack space needed for
a given task? 

I can estimate what _my_own_ stack requirements are, but 
how much more do I have to plan for the "ecos" stuff? When 
I ran these tasks I assumed that 8K were going to suffice,
but evidently that was not the case. Now, bitten once, I
jacked up the size to 32K, but that is probably an overkill,
and I can get away with it because my system has several
megabytes of memory. 

But besides the fact that having a lot of memory doesn't
mean that you have to throw it away, a lot of folks out 
there do not have this luxury and have to make much more
reasoned assessments.

Is there a rule of thumb that the "gurus" out there use?

Thanks
Tony


____________________________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2004-05-23 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24  4:08 Anthony Tonizzo [this message]
2004-05-24 12:35 ` Nick Garnett
  -- strict thread matches above, loose matches on Subject: below --
2004-05-25  3:29 Anthony Tonizzo
2004-05-25  8:51 ` Nick Garnett
2004-05-24  4:51 Arkadi Grosman
2004-05-24  9:13 ` Andrew Lunn
2004-05-23 16:41 Anthony Tonizzo
2004-05-23 20:03 ` Matt Jerdonek

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=GKAIOKFEACFEEEAA@mailcity.com \
    --to=atonizzo@lycos.com \
    --cc=ecos-discuss@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).