Re: IO::Tee not behaving correctly

as busunsl pointed out it's really hard to help without the fault code. Here's what I would try:

if it's a console program, run under the debugger, setting stop points at certain log statements you think are failing. Inspect the tee object before the print, explicitly flush (via the debugger) after you print, check the log file.
or, whereever you have tee print, right before insert an explicit print to STDERR a Data::Dumper the tee object

-derby

Comment on Re: IO::Tee not behaving correctly

Replies are listed 'Best First'.
Re: IO::Tee not behaving correctly by grinder (Bishop) on Mar 13, 2002 at 14:02 UTC
The trouble is that it's around 1300 lines, and it's an interface between our billing system and the accounts system, so I'm a little leery of showing it to all and sundry. What I'm after specifically is whether anyone has (extensive)? experience with IO::Tee and whether there are any common gotchas to be aware of. It is very annoying, because the pressure is on me to do something low-tech, like `print $var; print LOG $var` which is more prone to synchronisation errors (printing to the screen and not to the log). print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u'	[reply] [d/l]

Replies are listed 'Best First'.

Re: IO::Tee not behaving correctly
by grinder (Bishop) on Mar 13, 2002 at 14:02 UTC

The trouble is that it's around 1300 lines, and it's an interface between our billing system and the accounts system, so I'm a little leery of showing it to all and sundry. What I'm after specifically is whether anyone has (extensive)? experience with IO::Tee and whether there are any common gotchas to be aware of.

It is very annoying, because the pressure is on me to do something low-tech, like print $var; print LOG $var which is more prone to synchronisation errors (printing to the screen and not to the log).

print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u'

[reply]
[d/l]