-
Notifications
You must be signed in to change notification settings - Fork 7
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
Calltrace does not continue after first time hitting break
#4
Comments
Hm, I cannot reproduce this: python3 -m emdbg.analyze.calltrace -v --target px4_fmu-v5x_default --stlink --sample 60 -ex "px4_calltrace_spi_exchange"
python3 -m emdbg.analyze.calltrace -v --target px4_fmu-v5x_default --stlink --sample 60 -ex "break spi_exchange" Perhaps it's because I'm using an STLink, let me try with a JLink. |
Thank you. |
Hm, that sucks. What GDB version are you using ( python3 -m emdbg.analyze.calltrace -v --target px4_fmu-v5x_default --stlink --sample 60 -ex "load" -ex "break spi_exchange" |
|
Oh I thought it was a typo at first. I'll check if I can find a v5 somewhere. But at first glance it looks pretty similar to the v5x.
|
|
Hm, maybe it's a dependency problem? Here's what I have installed:
Probably not relevant for these issues:
|
Thank you. |
I'm not sure what else could be the problem… did this magically solve itself? |
TL;DR
px4_breaktrace
does not continue to run afterbreak
despitecontinue
The MCU halts forever and thus only one function call is sampled.
What?
I want to create a callgraph for some SPI function. To do so, I run:
python3 -m emdbg.analyze.calltrace -v --px4-dir ~/PX4-Autopilot --target px4_fmu-v5_default --jlink --sample 60 -ex "px4_calltrace_spi_exchange"
with
px4_calltrace_spi_exchange
defined like this infmu.gdb
:Expected behavior
The MCU should continue to run after hitting the break point.
Note: The function
px4_commands_backtrace
does callcontinue
afterbreak
and someprintf
The text was updated successfully, but these errors were encountered: