Closed BlackOfWorld closed 2 years ago
Faced the same issue on Windows 10 build 1903. Any idea how to resolve this?
Seems like this only applies to vmware with AMD cpu (for me at least)
You cant use ByePg in combination with WinDbg due to the Hal interface being modified.
Oh yes, I read an issue that was posted here, you're right I completely forgotten about it. It's something to do with VirtualKD I believe and not with the hal interface itself? Correct me if I'm wrong. I'll try it without VirtualKD and then without any debugging at all (I wish I could use SoftIce, but it's only for windows xp). Anyways thanks for the response!
You're more than welcome, my apologies for the super late response, it must have got lost in my notification.
Any form of KD should break in theory so it likely won't make any difference. I'd recommend using a hypervisior debugger like VMWare GDB stub if that's an option.
You're more than welcome, my apologies for the super late response, it must have got lost in my notification.
Any form of KD should break in theory so it likely won't make any difference. I'd recommend using a hypervisior debugger like VMWare GDB stub if that's an option.
Problem with GDB is, that it doesn't load any of my symbols without some special settings (I might look into that deeper later). I did try and get in touch with you on OSDev discord server, but you have both DMs and friend requests disabled. Again, thanks for the reply! I was starting to slowly doubt my issue will never be fixed 😄
Closing due to inactivity and that the problem was explained and solved.
Title says all. It's not the ExHook fault's, according to the debugger it's hangs the machine at https://github.com/can1357/ByePg/blob/master/ByePgLib/ByePg.cpp#L46
Any solutions/workarounds?
Verbose output:
Here's a screenshot of windbg:![image](https://user-images.githubusercontent.com/16164933/102716633-71d62f80-42dd-11eb-9fdd-24720d5793e4.png)