-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Provide Project File #1909
Comments
There is a settings file and databases per debuggee. |
Any documentation on where to find and use it? I can't find anything about this feature. Nothing like for other programs File->open project. Also:
|
Databases are saved and loaded automatically, you don’t have to do anything. |
It doesn't keep the working directory and arguments I passed to an executable though, when I reopen it for debugging. |
As a solution in the meantime you can construct the command that launches your application with the desired command line and working directory and add it as a favourite:
|
That first issue only refers to command line arguments, that can be achieved by an implementation that doesn't use a project file. A project file can store a lot more information than just the command line arguments. It isn't exactly a duplicate. I did search, I didn't find anything with the keywords I used. |
So what would be stored in a project file? You mention command line, that is stored (minus that issue). Currently the databases store your labels comments breakpoints, what else do you want? The databases (similar to ida idb) are stored in the “db” folder |
The database file can be stored in/with the project file. Some people may want to use the same database for the same executable, like I do for a few projects. Program settings that are only applied for that specific project file. Sounds like database is basically what the project file is, just need to change it so it isn't hidden from the user in such a manner as it currently is. |
You can import/export the database from the file menu if you want to share it with your peers (or just copy the relevant file from the db folder). As for program settings, I assume you mean the x64dbg options (x64dbg.ini)? This you can also share with your peers (in fact the whole x64dbg directory is portable, nothing is hidden). The plugin system is more than rich enough to implement a more advanced system that suits your needs better... |
Provide some sort of project file system. So that targets and settings don't have to be constantly re-entered manually.
Also don't close/clear the debugger when the program has finished executing.
The text was updated successfully, but these errors were encountered: