You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So maybe watchpoint expressions with result "undefined" are not reported correctly.
======================
My main motivation for looking here, was the behavior of watchpoints with regard to package scope changes.
In my application I had my %hash;
along with some imported modules.
When my hash was populated completely (and should be constant afterwards), I wanted to see where and when $hash{'myEntry'} changed unexpectedly. But using a watchpoint w $hash{'myEntry'} in the debugger led to a lot of unwanted breaks: each time the package/module scope changed the visibility of %hash changed also, of course.
How these visibility changes can be ignored in watchpoint breaks, I do not not know yet (should this be another bug report?).
The text was updated successfully, but these errors were encountered:
hexcoder-
changed the title
perl5db.pl: handling of undefined _DB__handle_watch_expressions()
perl5db.pl: handling of undefined watch_expressions in_DB__handle_watch_expressions()
May 10, 2024
hexcoder-
changed the title
perl5db.pl: handling of undefined watch_expressions in_DB__handle_watch_expressions()
perl5db.pl: handling of undefined watch_expressions in _DB__handle_watch_expressions()
May 10, 2024
(This is just an observation, not necessarily a bug.)
perl5db.pl as of commit c60ffc1
Module: perl5db.pl
Description
Reviewing the code for
_DB__handle_watch_expressions()
perl5/lib/perl5db.pl
Line 2483 in 8cacb84
I found that using
join
hereperl5/lib/perl5db.pl
Line 2494 in 8cacb84
makes
$val
always defined, sincejoin
always returns a (possibly empty) defined string.Then in the following line
perl5/lib/perl5db.pl
Line 2495 in 8cacb84
the false branch is never applied.
So maybe watchpoint expressions with result "undefined" are not reported correctly.
======================
My main motivation for looking here, was the behavior of watchpoints with regard to package scope changes.
In my application I had
my %hash;
along with some imported modules.
When my hash was populated completely (and should be constant afterwards), I wanted to see where and when
$hash{'myEntry'}
changed unexpectedly. But using a watchpointw $hash{'myEntry'}
in the debugger led to a lot of unwanted breaks: each time the package/module scope changed the visibility of %hash changed also, of course.How these visibility changes can be ignored in watchpoint breaks, I do not not know yet (should this be another bug report?).
The text was updated successfully, but these errors were encountered: