Probably just catching stdout/stderr is needed?

see http://stackoverflow.com/questions/8184827/powershell-capture-the-output-from-external-process-that-writes-to-stderr-in-a

alternatively try to see if die() raises an exception ...

see http://stackoverflow.com/questions/20637600/catch-perl-errors-from-powershell-script

PS: FWIW, found the links by googling your title!

update

tested, you need to catch STDERR

PS C:\Windows\system32> $cmdOutput = perl -e 'die(1)' 2>&1
PS C:\Windows\system32> echo $cmdOutput
perl.exe : 1 at -e line 1.
Bei Zeile:1 Zeichen:18
+ $cmdOutput = perl <<<<  -e 'die(1)' 2>&1
    + CategoryInfo          : NotSpecified: (1 at -e line 1.:String) [
+], Remot
   eException
    + FullyQualifiedErrorId : NativeCommandError
[download]

this looks like there are other options to catch RemoteException from within PS, but unfortunately that's OT and not my expertise.

FWIW: I tested a PS try but it didn't catch.

> this looks like there are other options to catch RemoteException from within PS

see http://stackoverflow.com/questions/17548621/how-to-catch-external-command-failure

for a generic way to catch $lastexitcode

function Exec
{
    [CmdletBinding()]
    param(
        [Parameter(Position=0,Mandatory=1)][scriptblock]$cmd,
        [Parameter(Position=1,Mandatory=0)][string]$errorMessage = ($m
+sgs.error_bad_command -f $cmd)
    )
    & $cmd
    if ($lastexitcode -ne 0) {
        throw ("Exec: " + $errorMessage)
    }
}
[download]

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!}

Welcome, you're going to have to give details, are you checking the return from the perl script within powershell, are you doing anything based on this? When posting various sensible suggestions are made, e.g. How do I post a question effectively?.