Re: [lwip-members] new debugging features in CVS

[Jani Monoses]

This looks nice.
But does this mean lwipopts.h must define every modules' debug flag?
Can't the behaviour of old debug.h includes lwipopts.h be preserved
where debug.h defines every previously undefined (in lwipopts) macro.
This way all flags are guarranteed to have a value and that will be
core lwip and updated when new flags are added to the code.
So IMHO lwipopts should just tune things not provide them all.
Or am I missing something?






> Hello,
> 
> in the latest CVS tree, the debugging configuration (previously
> in debug.h) is now in your lwipopts.h file, which must now
> contain the debug settings:
> 
> #ifndef __LWIPOPTS_H__
> #define __LWIPOPTS_H__
> 
> #include "lwip/debug.h"
> 
> ...
> usual lwIP configuration goes here
> ...
> 
> /** debug configuration */
> #ifdef LWIP_DEBUG
> 
> /** Enable only debug messages matching any of these types
>  *  (add DBG_ON if you want to see all enabled module messages
>  *  regardless of type).
>  */
> #define DBG_TYPES_ON (DBG_ON | DBG_TRACE | DBG_STATE | DBG_FRESH)
> 
> /**
>  * Enable/disable debugging per module
>  */
> #define DEMO_DEBUG       DBG_OFF
> #define ETHARP_DEBUG     DBG_ON
> 
> # ...
> 
> #define TCPIP_DEBUG      DBG_OFF
> #define TCPDUMP_DEBUG    DBG_OFF
> #define DHCP_DEBUG       DBG_ON
> 
> #endif /* LWIP_DEBUG */
> 
> Regards,
> 
> Leon Woestenberg
> 
> 
> 
> 
> 
> _______________________________________________
> lwip-members mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/lwip-members