You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This may be intended in some way, but when cutter has a .rzdb project file opened up, if you try to attach the debugger to a running process, the list of processes is completely blank.
To Reproduce
Steps to reproduce the behavior:
Create a new project & save it as a .rzdb file.
Reopen the project from the file.
Open the "Debug" dropdown.
Click on "Attach to process".
No processes appear inside of the menu.
Expected behavior
Should show a list of processes that are currently running that can be attached to.
Screenshots
Additional context
The issue does not occur if a file is simply opened up without being part of a project file.
The text was updated successfully, but these errors were encountered:
I am surprised that even "All processes" list is empty. I could imagine how projects could break the upper list which filters by current file name, but that shouldn't affect all process list.
Environment information
Only tested on PE32
Describe the bug
This may be intended in some way, but when cutter has a
.rzdb
project file opened up, if you try to attach the debugger to a running process, the list of processes is completely blank.To Reproduce
Steps to reproduce the behavior:
.rzdb
file.Expected behavior
Should show a list of processes that are currently running that can be attached to.
Screenshots
Additional context
The issue does not occur if a file is simply opened up without being part of a project file.
The text was updated successfully, but these errors were encountered: