On Sat, 23 Jun 2001, Stas Bekman wrote:
> this works too:
> my $oldfh = select(STDERR); $| = 1; select($oldfh);
> print STDERR "stderr\n";
>
> I thought STDERR is unbuffered by default. Do you mangle with it? If so,
> how come warn() has it unbuffered?
modperl doesn't mess with it, not sure whats going on here.
> While we are on this point, it'd be nice to be able to tell the Test suite
> not to delete the log files on server restart. For two reasons:
>
> 1) be able to refer to older logs
> 2) have the logs open via tail -f all the time
try it, this already works by default.
> of course by default these should be disabled. May be --keep-logs, or some
> other flag that might group a number of features suitable for debugging
> (without gdb). In fact I suggest to use --debug for normal debug (e.g. as
> a group tag for --keep-logs, raising the trace prints level to 'debug' and
> more to come), whereas the current --debug should be --gdb or similar.
t/TEST already keeps the logs around, it only deletes them if you say
t/TEST -clean (which 'make test' does)
> so to summarize my suggestion:
>
> - s/debug/gdb/
> - add --keep-logs flag (Getopts: "keep-logs")
> - add --loglevel flag (Getopts: "log-level=s")
what loglevel is this? apache LogLevel or Apache::TestTrace level?
i don't want to add anything called 'gdb', wouldn't mind replacing the
current -debug with -debugger, but the idea is the test suite should start
gdb, dbx, or whatever debugger is appropriate.
but then the 't/TEST -d' shortcut would nolonger work, which i kinda like.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
