As best I can tell, this is only with ithreads. Vanilla 5.8.8 (or with most recent Time::HiRes from CPAN), NYTProf 2.07, or with most recent from svn: $ ~/Sandpit/588ig/bin/perl5.8.8 -w -T -d:NYTProf -MTime::HiRes -e0 Unable to determine line number in -e. Unable to determine line number in -e. Unable to determine line number in -e. Unable to determine line number in -e. Unable to determine line number in -e. Current maint-5.8, NYTProf 2.07, or with most recent from svn: $ ~/Sandpit/snap5.9.x-34928/bin/perl5.8.9 -w -T -d:NYTProf -MTime::HiRes -e0 Unable to determine line number in -e. Insecure dependency in require while running with -T switch at /home/nick/Sandpit/snap5.9.x-34928/lib/perl5/5.8.9/vars.pm line 8. BEGIN failed--compilation aborted at /home/nick/Sandpit/snap5.9.x-34928/lib/perl5/5.8.9/vars.pm line 8. Compilation failed in require at /home/nick/Sandpit/snap5.9.x-34928/lib/perl5/5.8.9/x86_64-linux-thread-multi/Time/HiRes.pm line 4. BEGIN failed--compilation aborted at /home/nick/Sandpit/snap5.9.x-34928/lib/perl5/5.8.9/x86_64-linux-thread-multi/Time/HiRes.pm line 4. Compilation failed in require. BEGIN failed--compilation aborted. Um, not good. Particularly not good as I don't know why. It's failing TAINT_PROPER("require"); inside pp_require for the BEGIN block generated by use strict qw(vars subs); in vars.pm No, I don't know why. Or, more importantly, what chain of events is causing PL_tainted to become set, and therefore what the cause is, and therefore 1: how serious it is 2: how to fix it Of course, Tim and I are both busy tomorrow, although he's busier than me: http://conferences.yapceurope.org/lpw2008/schedule Nicholas ClarkThread Next