Debugging multithreaded driver


I'm trying to follow a driver's trace but much too often an event on
other channel arrives and the trace gets messy and starts jumping back
and forth, rendering the trace completely unreadable.

My example is going through a heavy user add operation while a modify
user flows from the connected system. The trace goes back and forth
between the events and it's hard to tell apart query results and the
modify event.

Is there any way to automatically tell when it's hopping from one event
to the other?
Should I perhaps limit the driver to 1 thread anyways? Is that even
I thought about using the event-id but from what I've read so far it
doesn't look
too consistent and is more a "best effort" type.


YLivay's Profile:
View this thread:

Parents Reply Children
No Data