Closed epasveer closed 1 year ago
Looking at the code, it is already only called for run/start modes. It is not called for connect/attach.
I'm thinking the user is starting the embedded app with the wrong mode. Should use "attach". Not "run/start".
When I get my embedded test environment, I will look at improving the "connect/attach" modes.
For now, it is only set to turn on randomization. If the Seer config says to turn it off, the setting is not used. So this will prevent any call to gdb, thus avoiding the error message.
So turn it off in Seer's config page under the gdb tab.
Closing task. Reopen or create a new task if required.
Randomizing the start address is not always supported for all platforms. Specifically, it should only be used for run/start modes.
Also, instead of bringing up an error dialog, just print the error to the status bar.