Hi,
Here's a small patch which implements NtQueryInformationProcess properly for ProcessInformationClass set to ProcessDebugPort.
It fixes cases when ProcessInformationLength != 4, but doesn't check if a debugger is present or not. Should it ? I don't expect that anyone would like to run Visual Studio on Wine to debug a Win32 program :-)
Laurent Pinchart
On April 2, 2002 12:17 pm, Laurent Pinchart wrote:
Hi,
Here's a small patch which implements NtQueryInformationProcess properly for ProcessInformationClass set to ProcessDebugPort.
It fixes cases when ProcessInformationLength != 4, but doesn't check if a debugger is present or not. Should it ? I don't expect that anyone would like to run Visual Studio on Wine to debug a Win32 program :-)
Why not??? I think that would be waaaay cool!
It fixes cases when ProcessInformationLength != 4, but doesn't check if a debugger is present or not. Should it ? I don't expect that anyone would like to run Visual Studio on Wine to debug a Win32 program :-)
sdk's windbg already work, so why no VC++ debugger ? btw, your patch will not compile (ret/retv)
A+
sdk's windbg already work, so why no VC++ debugger ?
Then we'll probably have to implement NtQueryInformationProcess completely for ProcessDebugPort. Does anyone know what it should return ? The debugger process handle ?
btw, your patch will not compile (ret/retv)
Sorry, I sent the wrong file. Here's the correct version.
Laurent Pinchart
sdk's windbg already work, so why no VC++ debugger ?
Then we'll probably have to implement NtQueryInformationProcess completely for ProcessDebugPort. Does anyone know what it should return ? The debugger process handle ?
the debugport value is not intented for ring3 use. so any non null value would do when the debugger is present.
A+
-
Dimitrie O. Paun -
Eric Pouech -
Laurent Pinchart