From: Gary Thomas <gary@mlbassoc.com>
To: Rupesh Kumar <rupeshk@moschip.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Problem with MGETHDR
Date: Mon, 13 Jun 2005 13:55:00 -0000 [thread overview]
Message-ID: <1118670937.13965.24.camel@hermes> (raw)
In-Reply-To: <1118670279.2593.28.camel@soctest>
On Mon, 2005-06-13 at 19:14 +0530, Rupesh Kumar wrote:
> Hi all,
>
> I am running the http server on eCos (MLB HTTP Server).
^^^^^^^^^^^^^^^
There is no such thing; there is a sample HTTP server setup on the MLB
website which uses standard eCos with a publicly available HTTP server.
I'm sure this is what you meant :-)
>
> In my ethernet driver eth_drv_recv function in in ISR Context.
> After Receving some packets eth_drv_recv function is failing.so i am not
> able to receive any more packets.
>
> I have found that eth_drv_recv() is failing at MGETHDR Macro call.At the
> time of failing it is not even entering the macro call.(this i found by
> putting some traces in the MGETHDR Macro Call).
What platform/target?
Most likely, something is going wrong in your application code,
possibly a stack overflow, etc.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-06-13 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 13:48 Rupesh Kumar
2005-06-13 13:55 ` Gary Thomas [this message]
2005-06-13 14:01 ` Gary Thomas
[not found] ` <1118671882.2593.37.camel@soctest>
2005-06-13 15:00 ` Gary Thomas
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=1118670937.13965.24.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=rupeshk@moschip.com \
/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).