-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stack and memory dump in trace browser #2378
Comments
Why hasn't anyone written anything? I was guessing this is a highly requested feature but there is no interaction. |
Crazy right? Almost like this is an open source project where nobody gets paid to implement anything... |
@mrexodia You're right. I'm sorry if I'm being rude. I'm just surprised there has been no comment on this issue in 2-3 years. |
You are welcome to contribute! If you have any questions feel free to drop them here or you can start a discussion/connect in one of the chats. |
I don't have any code written for this since 2020... It's very complicated. Every memory accesses in the trace would be indexed by a tree with key {address, traceindex} in order to find the current content at any address at any instruction execution very fast. The index may need to be stored in the trace at the end of tracing or when closing the trace file. |
I'm still planning to start on this in 2023. If anybody is interested, leave a message here. |
My TODO list
|
Add call stack and memory dump in trace browser, based on information available in trace file. This requires the trace file be scanned from current selected instruction up to the first one.
(I'm working on this, let me create an issue first, currently there is no dump or stack window in trace view, references and log view will be used first)
The text was updated successfully, but these errors were encountered: