public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Alexandre <thekyz@gmail.com>
To: Alexandre <thekyz@gmail.com>,
	 	"eCos Mailing List" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Can excessive/intensive serial flow cause stack overflow?
Date: Thu, 03 Jul 2008 13:48:00 -0000	[thread overview]
Message-ID: <d5aafeec0807030647j3a6f4a20i3b5d4033762e24b4@mail.gmail.com> (raw)
In-Reply-To: <20080703101011.GC27831@lunn.ch>

On Thu, Jul 3, 2008 at 12:10 PM, Andrew Lunn <andrew@lunn.ch> wrote:
> LPC2106 is an ARM right?

It is indeed.

> First off, i would enable asserts in the INFRA package. It adds some
> CPU overheads, but that might actually help in your situation....

My software does not start anymore when I do that. Do I have to add
something ? I read on the documentation that the execution of code can
be halted by asserts if a condition is not met. Is it the problem ?

Thanks,

Alex

-- 
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:[~2008-07-03 13:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03  9:58 Alexandre
2008-07-03 10:10 ` Andrew Lunn
2008-07-03 13:48   ` Alexandre [this message]
2008-07-03 14:05     ` Andrew Lunn
2008-07-03 14:52       ` Alexandre
2008-07-03 14:54         ` Alexandre
2008-07-03 14:59           ` Alexandre
2008-07-03 15:07             ` Alexandre
2008-07-03 15:24               ` Andrew Lunn
2008-07-03 15:30                 ` Alexandre
2008-07-03 15:40             ` Andrew Lunn
2008-07-03 16:06               ` Alexandre
2008-07-03 19:11                 ` Sergei Gavrikov

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=d5aafeec0807030647j3a6f4a20i3b5d4033762e24b4@mail.gmail.com \
    --to=thekyz@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).