On 20-Apr-2000 Sean Hunter wrote:
> A way I use to catch races in userspace is to step the debugger into
> the race window, leave it halted there, and run the program normally
> in a seperate shell. This sort of thing means you can be guarranteed
> to hit the race every time. I wonder if we can't use the same
> principle in kernel-space? Have a special macro that we can insert
> into a suspected race window that will stop one processor and wait
> until another one hits the race window (or am I just talking
> bollocks?)
Eric Youngdale had/has a debug SCSI driver which blocks at every point a
driver is allowed to block. This is an excellent way to find deadlocks
and race-conditions.
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:17 EST