Introduced dump to trace

[torusrxxx]

This fixes #2378
There's obviously a lot more to do. This pull request is here only for those who desperately want to dump from a trace or want to become alpha testers.
Right click on an instruction in the trace, and click the "Information" menu to get full dump of the trace up to the selected instruction into the log view.

[torusrxxx]

The trace dump index is working and tested on a 136MB huge trace.
Speed is lightening. Search constant takes 10 seconds and memory reference search takes 46ms. When memory reference search is used for the first time it takes 17s including reading the trace file and building the index.
Memory usage is moderate. It saves a record in trace for every byte, so memory usage could be improved by saving a record for every dword instead. This is more complex due to special treatment needed for unaligned memory access. Currently it uses about 567MB for the 136MB test trace, may be acceptable.
Next step will be the GUI part.

[mrexodia]

Would you like this to be merged into development or will you continue development on this branch? Currently the format checks are failing, so merging is blocked...

[torusrxxx]

I think those new files are already formatted, no idea why appveyor doesn't like that. I'll pause development for a while, but I don't think this feature is completed. The aim of this pull request is to bring in dump and stack windows, not to merely accelerate memory reference search. Of course I support merging it if you think merging this would allow other people to use this feature and contribute to it. Possibly disable the debug feature of dumping the trace memory in log view when clicking on "information" menu, it should be available in the dump tab instead.

[torusrxxx]

Dump widget has been added to trace, now it looks almost like the CPU view. There are still tons of usability problems and random crashes.

[mrexodia]

It looks like this is conflicting with the changes in #3192 a bit. I will try to properly refactor the HexDump to take an AbstractMemoryPage with pure virtual read/write functions, since this will be useful for other projects as well.

[mrexodia]

The following files are causing the formatting checks error btw:

src/gui/Src/Tracer/TraceDump.cpp
src/gui/Src/Tracer/TraceDump.h
src/gui/Src/Tracer/TraceFileDump.cpp
src/gui/Src/Tracer/TraceFileDump.h

Might be CRLF vs LF?

[AppVeyorBot]

✅ Download x64dbg 1.0.1711 (commit ab2a69cd13 by @torusrxxx)

[AppVeyorBot]

✅ Download x64dbg 1.0.1725 (commit 3d0e2654a9 by @torusrxxx)

[torusrxxx]

Maybe refactor HexDump first, and then we continue from that?

[AppVeyorBot]

✅ Download x64dbg 1.0.1726 (commit f02671aeb3 by @torusrxxx)

[AppVeyorBot]

✅ Download x64dbg 1.0.1765 (commit ca0b06d70a by @torusrxxx)

[AppVeyorBot]

✅ Download x64dbg 1.0.1766 (commit 517b1ec646 by @torusrxxx)

[AppVeyorBot]

✅ Download x64dbg 1.0.1778 (commit 1ea8ab91d9 by @torusrxxx)

[torusrxxx]

DisableTraceDump setting has been added, it shouldn't break things horribly now.

[AppVeyorBot]

✅ Download x64dbg 1.0.1779 (commit 46c7849fee by @torusrxxx)

[AppVeyorBot]

✅ Download x64dbg 1.0.1784 (commit ae0467f80a by @torusrxxx)

[mrexodia]

Heya, hope you're doing well! Do you have a list of things left to do for this? It would be nice to eventually merge all the PRs, but I don't know how stable this is...

[torusrxxx]

I was busy as usual at the end of the year. I have finished using it back in October. I didn't test this since then. The stack window is missing. However it would require a bit of work which unfortunately could not be finished in 2023, and I think it's fine, you can already use the dump like a stack window. Then it would be in maintenance mode.

[AppVeyorBot]

✅ Download x64dbg 1.0.1855 (commit a609f1e98e by @torusrxxx)

[torusrxxx]

The stack is finally there!

[AppVeyorBot]

✅ Download x64dbg 1.0.1866 (commit 476db74b26 by @torusrxxx)

[mrexodia]

🥳 will give it a try ASAP!

[AppVeyorBot]

✅ Download x64dbg 1.0.1867 (commit 40e9c822bf by @torusrxxx)

[AppVeyorBot]

✅ Download x64dbg 1.0.1870 (commit a3a59e37b1 by @torusrxxx)

[torusrxxx]

Xrefs dialog is added so you can quickly find out what accessed this memory location. Extremely easy and fast.

[AppVeyorBot]

✅ Download x64dbg 1.0.1871 (commit b12e9ee114 by @torusrxxx)

[AppVeyorBot]

✅ Download x64dbg 1.0.1873 (commit 0a1fb28928 by @torusrxxx)