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
In 0.9.25 the debugger automatically opens default.raddbg_project on startup. Because of that, all previously configured targets and settings are available immediately.
In 0.9.26 and newer, default.raddbg_project does not appear to be opened automatically anymore. The debugger starts with an "Untitled Project" instead, so no targets are loaded. Once I manually open default.raddbg_project, the targets appear as expected.
In 0.9.27 (and possibly 0.9.26 as well), I can create a target, set its working directory, save the project file, close the debugger, and reopen the project file. The target is restored, but the working directory is not.
Looking at the saved .raddbg_project file, the working directory is written as an empty string even though a value was set in the UI:
In 0.9.25 the debugger automatically opens default.raddbg_project on startup. Because of that, all previously configured targets and settings are available immediately.
In 0.9.26 and newer, default.raddbg_project does not appear to be opened automatically anymore. The debugger starts with an "Untitled Project" instead, so no targets are loaded. Once I manually open default.raddbg_project, the targets appear as expected.
In 0.9.27 (and possibly 0.9.26 as well), I can create a target, set its working directory, save the project file, close the debugger, and reopen the project file. The target is restored, but the working directory is not.
Looking at the saved .raddbg_project file, the working directory is written as an empty string even though a value was set in the UI:
explorer_WfIyPJJ5o8.mp4