This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Question about ecos server performance
[SNIP]
> > The bug is as follows:
> >
> > 1) The server (eCos app) starts,
> > 2) Connect to the server with telnet, port 4000
>
> Then what? What do you have to do [from the "client" side] to
> evoke the crash?
Connect. That's all. My crash happens in less than 3000 bytes
of transferred data, always.
If you want, I can send you my entire environment but before I
do that I'll update CVS. Maybe it was a bad day when I downloaded?
> > 3) The server crashes.
> >
> > The server's stack is being corrupted. It fails with an illegal
> > instruction, the PC ends up at 0x0000 0004 (or around there, very
> > low memory) and GDB cannot (of course) trace the stack.
> >
> > It seems to happen when I run out of MBufs.
> >
> > I am using the tip of tree eCos, ecosconfig 2.11 and also
> > 2.3. I also used both net and new_net with similar results.
> > "new_net" allows gdb to continue to run, "net" disconnects
> > the GDB debugger entirely.
>
> I assume that you've only tried this on the PC?
Yes, it's all I've got currently.
I had a SIMILAR bug a LONG time back with an XScale but it would take
a long long time for it to crash and that very well could have been
application code.
-Rich
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss