Not exactly a high priority bug, but I found that if you set a breakpoint on
a line where a 'use' statement exists, the breakpoint will show as set and
the debugger won't complain:

$ perl -d

Loading DB routines from version 1.32
Editor support available.

Enter h or `h h' for help, or `man perldebug' for more help.

7:      print "hello!\n";
  DB<1> b 9
  DB<2> v
4:      use strict;
5:      use warnings;
7==>    print "hello!\n";
9:b     use Data::Dumper;
11:     print "goodbye!\n";
13:     exit 0;

But, if you 'c' from line 7, you skip over the breakpoint on 9 as if it
wasn't there. It isn't a huge problem (and I really should keep all of my
'use' statements at the beginning of the script), but I figured it was worth
a mention.

I couldn't figure out how to actually file a bug at and didn't have the
usual 'View/Report Bugs' that most modules have. I'm happy to file a bug if
someone could point me in the right direction.


Description: Binary data

Reply via email to