in reply to Producing minimal examples for crashers

Are you sure, that this is needed? I mean, practically, if a bug can be reproduced on each run, then it's matter of few minutes to find it. The real problem is when the bug is sporadic, 10 times it works, and then it does not. Reducing the code in this case is of no help, since you don't know when the bug will reveal itself. This kind of bugs take away most of the time.

Well, YMMV.

  • Comment on Re: Producing minimal examples for crashers

Replies are listed 'Best First'.
Re^2: Producing minimal examples for crashers
by DrHyde (Prior) on Jun 11, 2013 at 11:06 UTC
    Au contraire, if you have a large body of complex code tracking down problems can be surprisingly hard. The perl debugger is no help, because it's crap (most code that uses subroutine attributes will fail under it, for example - see this p5p thread), and it doesn't like some modules, such as Dancer.
[reply]

In Section Seekers of Perl Wisdom