https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028
--- Comment #339 from Mark Millard <marklmi26-f...@yahoo.com> --- (In reply to Andriy Gapon from comment #314) Thanks for clearing my muddled thinking about having a sufficiently known context for hwatchpoint specification. Unfortunately, my attempt at using db_hwatchpoint_cmd to automatically set up the monitoring seems to have lead to "WARNING !drm_modeset_is_locked . . ." as what visibly happens on detection --and is not providing for access to backtraces or such for the code doing the unexpected modification. If I did not mess up the db_hwatchpoint_cmd calls, I doubt that I have enough background knowledge to figure out what is going on or how to get it to allow providing the backtrace for the value change. -- You are receiving this mail because: You are the assignee for the bug.
