Conversation
|
In the long run I think what I'd rather do is have it so that the script prompts you the first time it's run for an output path (defaulting to the input path), and subsequently caches that path for future invocations. Alternatively, for your use case, something like an |
|
Yes, fully agree.
Yes, a combined solution which also solves #31 would be ideal. I think it could be like the Ghidra "Export Program" which has a small GUI for the path and checkboxes for different features in the exported files:
(Obviously it should remember all of this) Maybe even a "do-not-show this dialogue again"-option and another way to trigger the dialogue, because I actually re-export my files very often while improving symbols (which is also why #31 became necessary).
I think catching the error is probably better than just testing
Yes, it's a horrible solution. |

This is merely a feature proposal.
Ideally the user could control the output path.
In my case, I mount disk images and analyze/decompile files in those.
These disks are typically read-only, so writing the file to the
exe_pathwill fail.My workaround is to move it to
/tmp/which works fine on Linux and macOS.