-
Notifications
You must be signed in to change notification settings - Fork 261
Comparing changes
Open a pull request
base repository: Marus/cortex-debug
base: master
head repository: Marus/cortex-debug
compare: rtosSupport
- 13 commits
- 9 files changed
- 1 contributor
Commits on Jan 7, 2018
-
Configuration menu - View commit details
-
Copy full SHA for c7654d0 - Browse repository at this point
Copy the full SHA c7654d0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 263f9d2 - Browse repository at this point
Copy the full SHA 263f9d2View commit details -
Added utility function for processing data from MINodes
This should be refactored to have utility functions for MINode data processing.
Configuration menu - View commit details
-
Copy full SHA for 036d07a - Browse repository at this point
Copy the full SHA 036d07aView commit details -
Updated execution flow requests to take a thread parameter.
Also replaced StoppedEvent from the debug-adapter as it doesn’t implement the full protocol for some reason.
Configuration menu - View commit details
-
Copy full SHA for 6aa9674 - Browse repository at this point
Copy the full SHA 6aa9674View commit details -
Removed hard-coded thread ID, and added a “current” thread ID that is…
… used for asynchronous execution events.
Configuration menu - View commit details
-
Copy full SHA for ea3f670 - Browse repository at this point
Copy the full SHA ea3f670View commit details -
Updated the threadsRequest to load an actual list of threads.
This will perform the following GDB requests: -thread-list-ids * This will retrieve a list of the current thread ID numbers, and the current thread ID number. -thread-info <id> * This is called for each thread ID to load details about the thread. If no thread is selected will select an aribtrary thread as current (this is typically only the case on fresh restart). In theory -thread-info with no paramter should retrieve the information about all threads at once; when I was testing I was getting inconsistent results. (-thread-info may only return one thread, but -thread-list-ids might have multiple). Still trying to determine the source of this issue.
Configuration menu - View commit details
-
Copy full SHA for 903d7e5 - Browse repository at this point
Copy the full SHA 903d7e5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 765e7a5 - Browse repository at this point
Copy the full SHA 765e7a5View commit details -
Updated stack trace request to get the stack trace for a specified th…
…read (instead of the GDB selected thread)
Configuration menu - View commit details
-
Copy full SHA for 2ad9344 - Browse repository at this point
Copy the full SHA 2ad9344View commit details -
Configuration menu - View commit details
-
Copy full SHA for c4e0825 - Browse repository at this point
Copy the full SHA c4e0825View commit details -
Configuration menu - View commit details
-
Copy full SHA for ba402ae - Browse repository at this point
Copy the full SHA ba402aeView commit details
Commits on Jan 8, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 34fe414 - Browse repository at this point
Copy the full SHA 34fe414View commit details
Commits on Jan 14, 2018
-
Configuration menu - View commit details
-
Copy full SHA for 2e77d7e - Browse repository at this point
Copy the full SHA 2e77d7eView commit details
Commits on Jan 15, 2018
-
Configuration menu - View commit details
-
Copy full SHA for be8c05f - Browse repository at this point
Copy the full SHA be8c05fView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...rtosSupport