This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: debug TCP/IP?
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: 张 亮 <johnsonest at hotmail dot com>
- Cc: ecos-discuss at sources dot redhat dot com, jifl at eCosCentric dot com
- Date: 15 May 2003 10:29:04 +0100
- Subject: Re: [ECOS] debug TCP/IP?
- References: <Law14-F29nlT2NqFJ3s0001bbf3@hotmail.com>
张 亮 <johnsonest@hotmail.com> writes:
> hi,every one.
> How can I debug the ecos TCP/IP stack? not just test it.because if
> i test failed,how can i trace and resolve the problem?
>
There are various options to enable debug diag_printf()s in both the
TCP/IP stack and in some ethernet device drivers. And you can always
just use GDB to track an execution path.
But you shouldn't really need to debug the stack itself. Any problems
you are having are most likely to be in the ethernet device
driver. The stack itself has been running successfully in eCos and
FreeBSD for many years.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com/ The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss