gdb internal error in finish_step_over()
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
Hi,
I have used the same GDB macro in OpenOCD and pyOCD and in pyOCD it fails with an internal gdb error.
I don't know how reproducible my scenario is, but I have a target device that is repetitively calling a function and I had a breakpoint that was printing arguments and continuing execution.
break some_function
commands
silent
if argument == value
printf "some message\n"
print other_argument
print yet_another_argument
end
continue
end
After some cycles (~ 20) gdb would fail with:
internal-error: int finish_step_over(execution_control_state*): Assertion `ecs->event_thread->control.trap_expected' failed.
There are open bugs in GDB for this messages (eg. this one) but since the problem is not happening with OpenOCD I'm opening an issue here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No pyOCD file or test is named. Start by reproducing the reported GDB macro failure against pyOCD and compare it with OpenOCD, then trace the execution and step-over handling associated with finish_step_over(). Done means the scenario is characterized and the internal error is addressed or its pyOCD-specific cause is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100