Comments (1)
In general for multithreaded debugging front ends rely on the threading support within GDB. This is not to say you couldn’t in theory implement RTOS support at a higher level and interpret the in memory structures and stack directly in the front-end tools, this just isn’t how things are typically implemented. Most front-ends, the cortex debug extension included, wrap around the support in GDB.
When it comes to threading support in GDB for RTOSs this support is provided by the GDB server - either built into the server as in OpenOCD (and enabled by a configuration command) or via plugins for the GDB server like J-Link (it is shipped with two plugins, FreeRTOS and Segger’s own embOS - but in theory additional ones can be written).
Why this is part of the GDB server and not as plugins/part of GDB itself I’m unsure - seems to me like it would have made more sense for it to be GDB plugins - but I’m sure there is some architecture reason why it is done at the server level.
from cortex-debug.
Related Issues (20)
- gdbsever debugging is suddenly unavailable, everything was fine before
- loadFiles not working as expected with PE Micro servertype HOT 3
- Default value of "Live Watch Refresh Rate" should be a number HOT 1
- Installed extension failure
- Peripherals, registers, memory and disassemble all read "There is no data provider registered that can provide view data." when using the attached SVD file. HOT 6
- Missing variables in the Variables View HOT 1
- Live watch not updating value on esp32s3 with esp-prog; "Warn : [esp32s3.cpu0] target not halted" HOT 2
- Windows/WSL, debugger attempts to open unix-style file HOT 2
- Project status, is it still actively developed/maintained? HOT 2
- Status of this extension HOT 3
- GDB session ended. but the debug toolbar won't close. HOT 13
- OpenOCD stdout not showing up in the DEBUG CONSOLE HOT 9
- To what extent does this extension rely on plugins for the JLink GDB server? HOT 4
- Peripheral Register/SVD Error HOT 1
- Slow listing of threads when hitting breakpoint HOT 6
- ram .data section error (all FF) when debug (run to main) armclang build + jlink HOT 4
- NUCLEO-H503 Debug Support HOT 1
- Bug: " Connecting to a QEMU gdbserver HOT 1
- Bug: unknown command: 'halt' when connecting to a QEMU gdbserver HOT 1
- Debug issues on Mac M2 in Visual studio code. -86 error code HOT 2
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 cortex-debug.