Hiya,
I just hit a trap in a d3d8 test I was running, and winedbg isnt showing the module information (I've put a manual DebugBreak in, and stepped through the call to a fixme, and I see no info!). This was on my temporary wine machine, so I dont know if its ever worked before, but I have a basic (cvs) install, no special info.
I am sure winedbg used to show the d3d8 functions in the past. Note that because they are in COM routines, they dont have to be exports, but I dont know if they are or not. nm d3d8.dll.so does seem to show the entrypoints, so is there anything I am missing - configuration wise, setup wise etc?
Jason
Ann and Jason Edmeades a écrit :
Hiya,
I just hit a trap in a d3d8 test I was running, and winedbg isnt showing the module information (I've put a manual DebugBreak in, and stepped through the call to a fixme, and I see no info!). This was on my temporary wine machine, so I dont know if its ever worked before, but I have a basic (cvs) install, no special info.
I am sure winedbg used to show the d3d8 functions in the past. Note that because they are in COM routines, they dont have to be exports, but I dont know if they are or not. nm d3d8.dll.so does seem to show the entrypoints, so is there anything I am missing - configuration wise, setup wise etc?
are you modules compiled with debugging info ? A+
-
Ann and Jason Edmeades -
Eric Pouech