This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Debug output
- To: Jonathan Larmour <jlarmour at redhat dot com>
- Subject: Re: [ECOS] Debug output
- From: Gary Thomas <gthomas at cambridge dot redhat dot com>
- Date: Wed, 13 Jun 2001 13:50:09 -0600 (MDT)
- Cc: eCos <ecos-discuss at sources dot redhat dot com>,
- Cc: eCos <ecos-discuss at sources dot redhat dot com>,"Trenton D. Adams" <tadams at extremeeng dot com>
- Organization: Red Hat, Inc.
On 13-Jun-2001 Jonathan Larmour wrote:
> "Trenton D. Adams" wrote:
>>
>> I noticed that my serial I/O is sending some debug info too if I run my
>> ROM based program. Running the RAM based programming using RedBoot
>> doesn't send this information to the serial port, but does send it back
>> to GDB.
>>
>> Network stack using 65536 bytes for misc space
>> 65536 bytes for mbufs
>> 131072 bytes for mbuf clusters
>> serial example is working correctly!
>>
>> I'm using TCP/IP to connect so I can use the serial port separately from
>> the GDB connection.
>>
>> How do I get rid of this? I assume it's an option in the eCos config,
>> but I can't seem to find it.
>
> I'm not entirely convinced about it's use now myself. When the TCP/IP stack
> was new it was informative, but now we could make it optional.
>
> For you, work around it by editting net/tcpip/current/src/ecos/support.c,
> in the function cyg_kmem_init().
>
> Gary, any reason not to make a config option that controls debug output. It
> could be a component that included other things like DHCP_CHATTER.
That would be fine. These messages are indeed vestiges of early testing of
the stack.