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
This is an issues that is an high-level outline of what should be supported in 0.1:
Native debugging
Catch crash: If the debugged program crashes the user should be able to catch and see where it crashes.
The user should be greeted with a default view showing source view, output view and perhaps locals, and watch for native debugging.
The user should be able to select a executable to run, and optionally set a working directory and command line parameters for the executable.
Any changes made to the UI (added views, settings within the viewes) should be saved on closed down and restored when user opens up ProDBG again.
The user should be able to have different projects (for different executables) and load them at will with all settings intact.
Set breakpoints, add watch variables, inspect and change local vars.
Non-native debugging
Supporting non-native debugging (such as emulators for different systems) should be supported but perhaps may not be primary focus for 0.1 but the user should still be able to select a different (experimental backed) and expect to have correct settings for that backend that is restored in a correct fashion as it is for native debugging.
The text was updated successfully, but these errors were encountered:
This is an issues that is an high-level outline of what should be supported in 0.1:
Native debugging
Non-native debugging
The text was updated successfully, but these errors were encountered: