I'm working on a Linux / Apache / mod_perl2 / HTML::Mason site and am having a problem getting error reports when a used perl module is not compiling (due to syntax errors for example).

As a test, I wrote a file with syntax errors, "MyTestGarbage.pm" and placed it in my library path.

When I use MyTestGarbage; from a normal .pl script it dies during compilation complaining of syntax errors as expected.

However when I include it from the <%init> section of a Mason component, Mason (or mod_perl) silently ignore the errors and keep running.

I don't find out it hasn't loaded until I actually try to use the syntax errored module and find missing functions in its namespace.

I've tested die and warn and they show up just fine in the apache logs or the mason-generated error response page.

Does anyone have any idea why the module's compilation problems are not being reported, and if there is a way to see them?

Thanks,
Andrew.