lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] lwip debugging basics


From: Jonathan Larmour
Subject: Re: [lwip-users] lwip debugging basics
Date: Sat, 02 Jun 2007 13:42:16 +0100
User-agent: Mozilla Thunderbird 1.0.8-1.1.fc3.4.legacy (X11/20060515)

liamstask wrote:
Hi - I'm hoping to get some general info about how to set up lwIP for
debugging.  I've had a difficult time finding much in the way of info about
how this works at all, so any pointers would be much appreciated!

Is debugging generally done over ICMP?  Is there a way to pipe it through
another transport, ideally one that is not network-based?  Is there (however
terse) a description of how this works anywhere?

If you need to debug the stack, you need to avoid using the stack!

You need some other communications channel. I imagine on embedded boards, people use serial mostly. Then in the port you ensure that you define the macros LWIP_PLATFORM_DIAG and LWIP_PLATFORM_ASSERT appropriately in the arch/cc.h header file, and then you can also consider enabling various of the LWIP_DEBUG options in your lwipopts.h file. There's also statistics with LWIP_STATS, which are useful to debug memory issues.

Alternatively if you want to be able to use a proper debugger such as GDB, you should probably consider running lwIP on top of an OS that supports that, such as eCos (which already has an lwIP port... go to http://ecos.sourceware.org/ then download eCos 2.0, then upgrade to its current anonymous CVS repository source base).

Jifl
--
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------      Opinions==mine




reply via email to

[Prev in Thread] Current Thread [Next in Thread]