Inconsistency between cli and python breakpoints for ignore count tracking
Doug Evans
xdje42@gmail.com
Wed Nov 13 09:02:00 GMT 2013
Hi.
Does anyone have a reasonable explanation for why we do ignore_count
tracking for python breakpoints (even with a "stop" method) but not
for breakpoints that have a cli condition that doesn't trigger? The
inconsistency doesn't feel right to me.
ref: breakpoint.c:bpstat_check_breakpoint_conditions
if (cond && value_is_zero)
{
bs->stop = 0;
}
else if (b->thread != -1 && b->thread != thread_id)
{
bs->stop = 0;
}
else if (b->ignore_count > 0)
{
b->ignore_count--;
bs->stop = 0;
/* Increase the hit count even though we don't stop. */
++(b->hit_count);
observer_notify_breakpoint_modified (b);
}
More information about the Gdb-patches
mailing list