Reporting against 0.6.33: while debugging an application with huge data structures in memory, the Step Return function in the debugger ceases to work reliably. It takes ages to finish and/or the debugger suspends in internal (non-application) code, displaying a very long stack trace filled with perl5db.pl and overload.pm.
This is apparently caused by auto-dumping of subroutine return values in perl5db.pl in certain circumstances. Since these dumps are of no use to EPIC anyway, the fix is to turn off this feature by setting PrintRet=0 in the debugger options. With this bug fixed, EPIC is going to append that option automatically, except for mod_perl and remote debugging, where all options are stored in the debugger launcher script or in the Apache configuration.
Log in to post a comment.