Skip to content

Calltrace does not continue after first time hitting break #4

Description

@sebglatz

TL;DR

px4_breaktrace does not continue to run after break despite continue
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 in fmu.gdb:

define px4_calltrace_spi_exchange
    px4_breaktrace spi_exchange
end

Expected behavior

The MCU should continue to run after hitting the break point.
Note: The function px4_commands_backtrace does call continue after break and some printf

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions