[En-Nut-Discussion] stdout question

[Joe Doubek]

I guess I might have solved my problem. I created a "dummy" device just
like debug0.c does but only provided the open and close function calls
in the NUTDEVICE structure, and I assign stdout to that initially. Seems
to work... is there any pitfalls with doing things this way? -joe

-----Original Message-----
From: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of Joe Doubek
Sent: Wednesday, July 28, 2004 9:47 AM
To: en-nut-discussion at egnite.de
Subject: [En-Nut-Discussion] stdout question

Hello all, I'm trying to setup a device that can use stdout for debug on
a telnet session. I want to leave all my printf, etc. statements the
same as when I debug over a uart, but want to conditionally leave the
uart free (based upon a #define) to later be used by my application.
Right now if I don't assign stdout to anything on start up it appears my
printf statements cause my app to crash spectacularly. Is there a way to
initially assign stdout to a "dummy" device that goes nowhere until
someone connects and my telnet server has a valid stream to reassign it
to? -joe

_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion