-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue regarding CreateProcess #282
Comments
This is supported and tested normally, so there is something else going on. I can't seem to deduce what that is from the call stack. Are you able to send the EXE/PDB, or if not, send a minimal reproduction example, so that I can try to reproduce locally? I cannot reproduce this with any of my tests. |
Apologies, I have updated my initial message with more information. The issue might be the thread I am creating, not |
Can you unpack that? What is unique about the thread you are creating? The Scheduler UI is crashing, and it should work regardless of which processes/threads are created. |
Nothing really, the code for it is here: But it simply launches a process, allocates memory, loads a dll, and then waits for the process to terminate |
Ah okay, interesting, I think this might have to do with the |
Thank you, I really do appreciate it. I can then use this instead of Visual Studio for this project :) |
I'm trying to debug a process which is launched via
CreateProcessW
, but it doesn't seem like it's supported.Edit: So it turns out it is supported, but it just doesn't work very well. I can get around this issue by placing a breakpoint on one of these two lines:
I can then continue and it will be fine. If I place a breakpoint on anything above or below these and continue, I will get the error below
[Window Title]
Fatal Exception
[Content]
A fatal exception (code 0xc0000005) occurred. The process is terminating.
Press Ctrl+C to copy this text to clipboard, then create a new issue at
https://github.com/EpicGames/raddebugger/issues
Call stack:
Version: 0.9.11 [aed9a28]
[Close]
The text was updated successfully, but these errors were encountered: