Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Stack and memory dump in trace browser #2378

Open
torusrxxx opened this issue Jun 26, 2020 · 7 comments · May be fixed by #3098
Open

Stack and memory dump in trace browser #2378

torusrxxx opened this issue Jun 26, 2020 · 7 comments · May be fixed by #3098
Assignees
@torusrxxx
Labels
feature The issue requests a new feature.

Comments

@torusrxxx
Copy link
Member

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)
@mrexodia mrexodia added the feature The issue requests a new feature. label Jan 5, 2022
@requizm
Copy link

requizm commented Apr 24, 2023

Why hasn't anyone written anything? I was guessing this is a highly requested feature but there is no interaction.

@mrexodia
Copy link
Member

Crazy right? Almost like this is an open source project where nobody gets paid to implement anything...

@requizm
Copy link

requizm commented Apr 24, 2023

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.

@mrexodia
Copy link
Member

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.

@torusrxxx
Copy link
Member Author

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.

@torusrxxx
Copy link
Member Author

I'm still planning to start on this in 2023. If anybody is interested, leave a message here.

@torusrxxx torusrxxx self-assigned this May 2, 2023
@torusrxxx
Copy link
Member Author

torusrxxx commented May 7, 2023 •
edited

My TODO list

  • Create dump reconstruction object
  • Feed data into dump reconstruction object
  • Add find references dialog similar to xrefs
  • Add call stack view
  • Add dump view
  • Add unpack/dump support
  • Add find strings support
  • Add find pattern support
  • Write memory map into trace file
  • Add memory map view
  • Add modules view
  • Fix randomised module base in trace file
  • Replace tree implementation with custom one and add storage support

@torusrxxx torusrxxx linked a pull request May 18, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@torusrxxx torusrxxx

Labels
feature The issue requests a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Introduced dump to trace torusrxxx/x64dbg
3 participants
@mrexodia @requizm @torusrxxx