I'm having a bit of an issue with profiling (it's my first attempt at profiling) a syslogd post-processor that I've written, and I'm hoping perhaps some wise monk can give me some guidance, or at least a boot to the head.

The problem is this (using perl 5.10.1 on FreeBSD 8.0 amd64):

d13-sut# perl -d:DProf ./myperldaemon -d
panic: Devel::DProf inconsistent subroutine return at /usr/local/lib/p
+erl5/5.10.1/mach/Sys/Syslog.pm line 120.
Compilation failed in require at ./myperldaemon line 19.
BEGIN failed--compilation aborted at ./myperldaemon line 19.
[download]

Of course, line 19 is simply

use Sys::Syslog qw( :standard :macros );
[download]

The relevent part of Syslog.pm is:

    115 # And on Win32 systems, we try to use the native mechanism for
+ this
    116 # platform, the events logger, available through Win32::EventL
+og.
    117 EVENTLOG: {
    118     my $is_Win32 = $^O =~ /Win32/i;
    119
    120     if (can_load("Sys::Syslog::Win32")) {
    121         unshift @connectMethods, 'eventlog';
    122     }
    123     elsif ($is_Win32) {
    124         warn $@;
    125     }
    126 }


    816 sub can_load {
    817     local($SIG{__DIE__}, $SIG{__WARN__}, $@);
    818     return eval "use $_[0]; 1"
    819 }
[download]

So my question is: "Is it me? Is it Sys::Syslog? or is it DProf?"