Shlomi Fish reported:
2012-Sep-01:
Plans for today:
Report the segfaults in
Devel::Cover.Add more tests.
Respond to this message by Rocky Bernstein:
Blog about the grant on my blogs.perl.org blog
- Also mention the new CPAN distributions I have uploaded.
- Mention the fact I made use of the
b [filename]:[line]feature for debugging Games-Solitaire-Verify.- Done:
2012-Sep-02:
Plans for today:
Handle the correspondence on:
- http://www.nntp.perl.org/group/perl.perl5.porters/2012/09/msg191426.html
- Done:
- TODO : Add link.
Handle Rocky's comment on:
Put a reminder on https://rt.perl.org/rt3/Ticket/Display.html?id=114284 for applying the patch there.
- Done.
Write more tests for the debugger.
I added a test for the
Lcommand, but it only checks that breakpoints are listed and not watch expressions and actions.
- More tests are needed for it.
2012-Sep-04:
Plans for today:
Write more tests for the
Lcommand.
- Done.
Write more tests in general.
- Wrote some for
S. There are more commands inperldoc perldebugfollowing it that already have test coverage.2012-Sep-05:
Handled the merging of my existing branch into blead, now that the patch with some of my changes was incorporated into blead:
Reported a bug with a new patch:
2012-Sep-06:
Added a test for the
a [line] commandcommand and noticed a failure (which had been reported to perl5-porters).
- Corrected the
lib/perl5db.pland test now passes.Added a test for the
A linecommand.Added a test for the
A *command.Added two Bash functions to my
_Theme perl/coreto facilitate testing the entire perl core distribution, and running onlylib/perl5db.t.


I would like to see the ability to run module tests as if under perl -d. There are some differences between the debugger environment and the pure interpreter that can break things in the debugger.
Allowing test suites to run via test_harness using the developer would help catch those problems. It could also generate reports of edge cases and such that could help to make the debugger itself more robust.