Comments (7)
@kaspar030 It would be great if you could re-run this on the current
main
branch (which includes #48), withRUST_LOG=probe_run=debug
set. That should print some more information we can use to diagnose what's happening.
Done, here's the end of the output:
stack backtrace:
0: 0x0000139e - <unknown>
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(2000039c) -> 200003bc
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00001303 pc=0x0000139e
1: 0x00001302 - cortex_m_semihosting::hio::hstdout
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003bc) -> 200003c4
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00001245 pc=0x00001302
2: 0x00001244 - cortex_m_semihosting::export::hstdout_str::{{closure}}
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003c4) -> 200003d4
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00001177 pc=0x00001244
3: 0x00001176 - cortex_m::interrupt::free
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003d4) -> 200003e4
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00001231 pc=0x00001176
4: 0x00001230 - cortex_m_semihosting::export::hstdout_str
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003e4) -> 200003f4
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00000617 pc=0x00001230
5: 0x00000616 - app::func
[2020-09-01T20:49:41Z DEBUG probe_run] update_cfa: CFA changed Some(200003f4) -> 200003fc
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00000aa5 pc=0x00000616
6: 0x00000aa4 - riot_core::thread::cleanup
[2020-09-01T20:49:41Z DEBUG probe_run] lr=0x00000aa5 pc=0x00000aa4
7: 0x00000aa4 - riot_core::thread::cleanup
I guess the thumb bit needs to be ignored in the check that's mentioned above.
from probe-run.
Thanks for the report! #47 should fix the behavior of Ctrl+C while the backtrace is being generated. To investigate the broken backtrace, it would be great if you could provide the source code of riot_core
.
from probe-run.
7: 0x00000d20 - riot_core::thread::cleanup
8: 0x00000d20 - riot_core::thread::cleanup
in these situations we should check both the PC (printed) and SP (not printed); if both haven't changed in one iteration then the virtual unwinder has gotten stuck and we should stop it and print an error message. (I thought there was already some logic to check for this condition but maybe not)
from probe-run.
We do have such a check, but it seems like that isn't enough:
Lines 579 to 582 in e1964b8
from probe-run.
@kaspar030 It would be great if you could re-run this on the current main
branch (which includes #48), with RUST_LOG=probe_run=debug
set. That should print some more information we can use to diagnose what's happening.
from probe-run.
Yeah that sounds like the right fix. Can you try with #50 to see if that fixes it?
from probe-run.
Thanks a bunch!
from probe-run.
Related Issues (20)
- `probe-run` fails to build due to yanked dependency HOT 8
- Probe run error points to old trouble shooting section
- CMSIS_DAP is not recognised (fix available link to PR)
- probe-run fails with `thread 'main' panicked at 'no entry found for key'` on heavy traffic and (maybe) buggy global logger. HOT 2
- The erase-all flag erases entire chip unnecessarily on nrf5340 which affects performance HOT 7
- Allow single line log output HOT 6
- Feature request: Timestamps on RTT messages HOT 1
- probe-run cannot detect pico HOT 4
- println! unexpectedly prints the statement's location before the formatted string
- probe-run assumes stack fits within a memory region
- Add an optional flag to halt once Ctrl+C is pressed
- Cannot install probe-run on Mac M1 HOT 5
- Running app on STM32F4 crashes core with unrecoverable exception HOT 8
- --log-format is inconvenient when only timestamp must be added HOT 1
- Cannot execute binary file HOT 2
- Issues using `probe-run` with an fe310g002 microcontroller HOT 5
- RP 2040: "ARM specific error" HOT 2
- Wrong SRAM regions for STM32L4 HOT 3
- Using app-template - Timeout occurred during operation HOT 2
- release final version with deprecation notice
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from probe-run.