On 12 Mar 2013, at 16:22, Allan Odgaard mailinglist@textmate.org wrote:

On Mar 12, 2013, at 4:57 PM, Justin Catterall 100621.1@masonsmusic.co.uk wrote:

...

[…] Reading through the exception_handler.pm file I see that line 30 is 'require Carp::Heavy…'. When I tried to install Carp/Heavy.pm using cpan it said that the module is up to date.

Any suggestions on what's not right here?

Does running this (in a terminal) work:

/Users/justin/perl5/perlbrew/perls/perl-5.16.2/bin/perl -e 'require Carp::Heavy'

If not, you likely tried to install the module for the system default perl, but you need to install it for the version of perl that you installed via homebrew.

That command runs without error (I did a copy and paste to ensure no typos). To check it I replaced Carp::Heavy with Lies::DamnLies and got the expected error.

I forgot to mention this is TM 1.5.11 (1635).

I've looked at this some more and can't see what might be wrong.

On 13 Mar 2013, at 10:15, Paul McCann pmccann@gmail.com wrote:

Hi Justin and Allan,

that error message rings some distant bells for me: maybe it's related to Perl's taint mode? Why would we be seeing a taint-related problem after changing the binary that "perl" points to? Perhaps because the file "perlcheckmate.pl" in the Perl bundle's support folder has a slightly mysterious shell-out to perl with -T turned on: line 33 of that file reads

my @lines = `perl -Tcw "$file" 2>&1`;

I'm guessing that if your path to the new perl may not be secure, or something like that --as per taint's requirements-- that message you're seeing might come flying out the other end. See "perldoc perlsec" for what triggers taint mode.

Anyway, easy to check if I'm blowing my usual volume of hot air here: just remove the taint check (ie the "T" in the line quoted) and see if the error still appears. Then you can start the hunt in earnest!

Good luck, Paul

Thanks for the pointer, Paul. Unfortunately that doesn't seem to be the solution. I removed the "T", opened a script, ran it to check it worked and that was fine, but if I introduced an error I got the same "exception_handler.pm" error, and not the usual useful Perl error messages.

I might try a perl newsgroup.