https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267028
--- Comment #308 from Andriy Gapon <[email protected]> --- Knowing the approximate step where the problem happens and knowing which variable gets corrupted, you can break to ddb before the corruption but after the affected module is loaded and set a hardware watchpoint on the to-be-corrupted address. Also, perhaps QUEUE_MACRO_DEBUG could be of some help. But to me it looks like something writes (32-bit) 7 to a wrong memory location. -- You are receiving this mail because: You are the assignee for the bug.
