Danny Backx wrote:
>
> Not that I have a problem with adding your patch, but why would you want to
> send this to stdout?
>
Because I wanted the lib output interleaved with the output of my program so I
could figure out which lib things were happening at the times my program was
doing its stuff.
I tried 'app >& log' and 'app > log 2>&1' but the output did not seem to be
interleaving correctly ( or at all), with this patch it interleaves as I
expect.
Yes, it seems weird that it did not work using 2>&1 but it really did not seem
to be working.
> We already have stderr and any named file that you care about, including a
> mechanism to enter the process id in the file name.
> (setenv DEBUG_FILE "/tmp/debug.%p" )
>
<SNIP>
> Danny
>
> Todd Denniston wrote:
> > hehe, I suppose I could 'use the source' and send DebugUtil.c ouput to stdout
> > :)
> > looks like only two places to change, or perhaps set DEBUG_FILE=stdout
> >
> > Please find quick patch included.
--
______________________________________________________________________________
Todd Denniston, Code 6067, NSWC Crane mailto:[EMAIL PROTECTED]
I'd crawl over an acre of 'Visual This++' and 'Integrated Development
That' to get to gcc, Emacs, and gdb. Thank you.
-- Vance Petree, Virginia Power
