public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Felix R <felixr@mailinator.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: building/running tests without RedBoot
Date: Fri, 17 May 2013 08:17:00 -0000	[thread overview]
Message-ID: <1368778622279-232338.post@n7.nabble.com> (raw)
In-Reply-To: <1368532204034-231731.post@n7.nabble.com>

I got i new Issue with http_simple.

I added FileIO and SD-Card drivers. The FAT demo works with tests, with my
eclipse build it does not find the stdio functions.
Now, the http_simple demo (does not use stdio functions)  is working in
"build tests" but not in my eclipse project. when calling pbuf_free() it
gives me an Assert:

ASSERT FAIL: <3>memp.c[199]memp_overflow_check_element() detected memp
overflow!
ASSERT FAIL: <3>memp.c              [ 199] memp_overflow_check_element()                                                                       
detected memp overflow!

although CYGDBG_LWIP_MEMP_OVERFLOW_CHECK is set to 0!
Note: if i disable asserts globaly, it works fine with eclipse. The demo
Application worked with eclipse before i added FAT and SD (and
dependencies).

I got 2 issues now. No reference to sdtio and occuring asserts.

please help.

Felix



--
View this message in context: http://sourceware-org.1504.n7.nabble.com/building-running-tests-without-RedBoot-tp231726p232338.html
Sent from the Sourceware - ecos-discuss mailing list archive at Nabble.com.

-- 
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:[~2013-05-17  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 10:52 [ECOS] " Felix R
2013-05-14 11:50 ` [ECOS] " Felix R
2013-05-17  8:17   ` Felix R [this message]

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=1368778622279-232338.post@n7.nabble.com \
    --to=felixr@mailinator.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).