4 ms·
Yeah, one of my main debugging tasks right now is primarily limited by my SSD write speed. Instruction-level traces take 9gb at minimum, any more significant wo
by foone 12y ago
Yeah, one of my main debugging tasks right now is primarily limited by my SSD write speed. Instruction-level traces take 9gb at minimum, any more significant work takes quite a lot more.
- dman 12y agoHow are you generating the instruction traces? What format are you writing them to on disk?
- foone 12y agoOllydbg run traces and in a plain text format. I'm constrained by my target application only working on older versions of windows, so I can't easily insert a compression step in the log generation or switch to a more compact binary representation. (I'm currently looking into solutions like a custom filesystem driver, running a second VM and using internal networking to stream to a FUSE filesystem, or possibly even hooking the filesystem access of my debugger and inserting a compression step into WriteFile() calls)