TTD Calls and Memory analysis persistence
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
What is the feature you'd like to have?
Persistent TTD Analysis tabs between relaunches similar to ttd bookmarks
Is your feature request related to a problem?
Losing track of analysis tabs.
Are any alternative solutions acceptable?
Not really
Additional Information:
Basically on closing the program, i have to redo my ttd queries in the calls and memory windows but the ttd bookmarks are persistent. it would be nice to have the queries be persistent too.
Contributor guide
No contributing guide indexed for this repository
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
Start by examining how TTD bookmarks are persisted and compare that flow with the Calls and Memory analysis tabs. The work is complete when the TTD queries in those tabs are restored after closing and relaunching the debugger, without requiring them to be entered again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, reverse-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100