This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Thread error with large buffer
- To: "'Dan Conti'" <danc at iobjects dot com>,"'eCos mailing list'" <ecos-discuss at sources dot redhat dot com>
- Subject: RE: [ECOS] Thread error with large buffer
- From: "Trenton D. Adams" <tadams at extremeeng dot com>
- Date: Fri, 20 Jul 2001 08:43:55 -0600
- Organization: Extreme Engineering
> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com [mailto:ecos-discuss-
> owner@sources.redhat.com] On Behalf Of Dan Conti
> Sent: Thursday, July 19, 2001 5:00 PM
> To: eCos mailing list
> Subject: RE: [ECOS] Thread error with large buffer
>
> 4k is a lot of data to put on a stack. also note that you have 4000
> bytes, not 4k there.
>
If someone asked you the time, would you tell them 4:35 and 23 seconds?
If I didn't know that 4000 was not EXACTLY 4K, then I shouldn't be
programming let alone programming an embedded system.
> why not just make it static? also there are routines you can use to
> check the stack size and usage for a given thread. also you can
adjust
> the stack size for main (the default in a kernel i just glanced at
is
> 8k). also you can enable stack overflow checking.
>
> -Dan
>
This is a TEST program, I don't think it's really necessary to worry
about silly things like where stuff resides in memory, whether it's on
the stack or on the heap.