Net::Server - problem getting STDERR (or is it STDERR??)

So - I figured that if in procress_request() i was to call a procedure
that didn't exist... ie:

sub process_request {
&ksjdflksjdf;
}

then the error - "undefined subroutine &main::lsjdfklsjdf called at
../t.pl line xx." would go to STDERR.

But for some reason - this isn't true. I get other things to STDERR -
but for some reason this error message gets lost somewhere. Where does
it go?

The forked process should inherit the STDERR definition ... since
Net::Server redirects it to the logfile.

Any ideas why I'm not able to see this error message anywhere?

would a runtime error of that sort .. not go to STDERR?

perl -wc doesn't pick up this type of error either... as it
shouldn't. (it could be exported from another package).. so this is a
runtime error.. not compile time.. and it doesn't go to STDERR.

Jon

Re: Net::Server - problem getting STDERR (or is it STDERR??)

shutterstock wrote:
> So - I figured that if in procress_request() i was to call a procedure
> that didn't exist... ie:
>
> sub process_request {
> &ksjdflksjdf;
> }
>
> then the error - "undefined subroutine &main::lsjdfklsjdf called at
> ./t.pl line xx." would go to STDERR.

It does.

>
> But for some reason - this isn't true. I get other things to STDERR -
> but for some reason this error message gets lost somewhere. Where does
> it go?

You tell us. You haven't shown any code that does your STDERR
mangling.

>
> The forked process should inherit the STDERR definition ... since
> Net::Server redirects it to the logfile.
>
> Any ideas why I'm not able to see this error message anywhere?

With the code you provided? No.

> would a runtime error of that sort .. not go to STDERR?

No, it would not NOT go to STDERR.

> perl -wc doesn't pick up this type of error either... as it
> shouldn't. (it could be exported from another package).. so this is a
> runtime error.. not compile time.. and it doesn't go to STDERR.

Yes it does.

Paul Lalli