Open Bug 1234354 Opened 9 years ago Updated 2 years ago

Investigate hooking pfnLockCb to better understand driver crashes

Categories

(Core :: Graphics, defect, P3)

Product:
Core
Component:
Graphics
Type:
defect

Tracking

()

People

(Reporter: jrmuizel, Unassigned)

References

Details

(Whiteboard: [gfx-noted]) 

In bug 1207993 it looks like pfnLockCb failures are causing driver crashes. Having the error code for these failures would help a lot in understanding what's going on.
Aaron, how practical to hook this?

The user mode driver will call OpenAdapter10 and get back a D3DDDI_DEVICECALLBACK struct that contains a function pointer to pfnLockCb
https://msdn.microsoft.com/en-us/library/windows/hardware/ff568914%28v=vs.85%29.aspx
Blocks: 1207993
Flags: needinfo?(aklotz)
Whiteboard: [gfx-noted]

I'm clearing out some old needinfos. I'm not sure if this is still an issue or not.

(In reply to Jeff Muizelaar [:jrmuizel] from comment #1)

Aaron, how practical to hook this?

It really depends on the generated code in the DLL hosting the callback. Easiest thing to do is probably to attempt the hook and, if it fails for some reason, we can follow up with a fix to support the required opcodes.

Flags: needinfo?(aklotz)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.