Skip to content
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

Allow to decode stack for binaries at any location #7

Closed
Anton-V-K opened this issue Jun 23, 2016 · 2 comments
Closed

Allow to decode stack for binaries at any location #7

Anton-V-K opened this issue Jun 23, 2016 · 2 comments

Comments

@Anton-V-K
Copy link

The tool works fine when decoding stack trace for ELF/HEX at the Arduino's build directory.
In some cases the binaries may be old (i.e. not freshly built), and they are located at other directory.

Use case:

  1. Build a sketch and deploy it to a device.
  2. Continue development (i.e. modify the code).
  3. Receive crash report from a user for the deployed version.
  4. Feed old HEX/ELF to the decoder along with the stack trace.

At the moment the step 4 should be preceded with extra actions: get corresponding sources from VCS and build them.

@me-no-dev
Copy link
Owner

I will take a look at how to trigger file open dialog, if that is possible :)

@me-no-dev
Copy link
Owner

FIXED! if elf is not found a dialog will be shown to manually locate it
please download latest release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants