From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26505 invoked by alias); 24 May 2004 23:29:49 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 26498 invoked from network); 24 May 2004 23:29:48 -0000 Received: from unknown (HELO lycos.com) (209.202.220.160) by sourceware.org with SMTP; 24 May 2004 23:29:48 -0000 Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Mon, 24 May 2004 23:29:34 -0000 To: ecos-discuss@sources.redhat.com Date: Tue, 25 May 2004 03:29:00 -0000 From: "Anthony Tonizzo" Message-ID: Mime-Version: 1.0 X-Sent-Mail: on Reply-To: atonizzo@lycos.com X-Sender-Ip: 192.86.86.213 Organization: Lycos Mail (http://www.mail.lycos.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit Subject: Re: [ECOS] Error on Cyg_Counter::add_alarm X-SW-Source: 2004-05/txt/msg00282.txt.bz2 > If you enable assertions (always a good idea during > development) you will also enable stack checking. I did not have assertions enabled, and I should have known better. But after enabling the traces and providing my own cyg_assert_fail() I noticed that, with the stack back at 8K, the assertion comes immediately at the start of the DHCP process (network stack). So, the 8K might be plenty for a run-of-the-mill thread, but as soon as you begin adding things such as an entire network stack, things get ugly pretty quickly. The only course of action now it to raise the stack space until the assertions disappear, and then, as Arkadi recommended, give it some slack. 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