in reply to Stopping hanging commands (evals) within debugger

Just wrap your string eval in a block eval in which you set a %SIG{ INT } = sub{ die; }; ie:

    eval { local $SIG{ INT } = sub{die}; eval $_code };

[download]

If you also want to be able to break out of long-running opcodes, you'd have to look at setting local $ENV{ PERL_SIGNALS } = 'unsafe';.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

RIP Neil Armstrong

Replies are listed 'Best First'.
Re^2: Stopping hanging commands (evals) within debugger
by LanX (Saint) on Dec 17, 2012 at 00:35 UTC
    Excellent, testscript works fine! =)

    $|=1;
$_code=' sleep 1, print for (1..100)';
 
eval { 
   local $SIG{ INT } = sub{die;}; 
   eval $_code 
};
 
print "after interrupt";
 
eval $_code; # again w/o wrapper

    [download]

    I'll post again when I got it integrated within the debugger!

    Cheers Rolf

[reply]
[d/l]

In Section Seekers of Perl Wisdom