public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Rob Duncan" <rob.duncan@designmagnitude.com>
To: ecos-discuss@sourceware.org
Subject: [ECOS] eCos LWIP thread-safety
Date: Sun, 20 May 2007 15:57:00 -0000	[thread overview]
Message-ID: <be72a610705200856l77519711rb007ecfb77a78a92@mail.gmail.com> (raw)

I'm having some trouble understanding what the thread-safety
requirements for using LWIP are.  I've been through the archives on
the LWIP mailing lists where it's explicitly stated that the low-level
APIs are not thread-safe, but I can't find an equivalent description
of the high-level socket interfaces.  It appears to depend on how the
specific OS port was done.  The reason I'm looking at this is because
I'm getting the following assertion failure:

ASSERT FAIL: <6>pbuf.c[577]pbuf_free() pbuf_free: p->ref > 0

According to the LWIP archives this assertion is often evidence of a
violation of the stack's thread-safety rules.  I'm exclusively using
the socket APIs from a single thread, so I'm wondering whether I need
to take any additional steps to satisfy these requirements.  Can
someone with a better understanding of the eCos LWIP port comment?

On the other hand, I'm running with a rather miserly buffer
allocation, and I suppose it's possible that I'm tickling some other
bug in the pbuf code.

Any thoughts and suggestions are very appreciated.

Thanks,

Rob.

-- 
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:[~2007-05-20 15:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=be72a610705200856l77519711rb007ecfb77a78a92@mail.gmail.com \
    --to=rob.duncan@designmagnitude.com \
    --cc=ecos-discuss@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).