Saying that I have a very simple C program test.c
, which just prints "hello world", its name is a.out
coming from gcc test.c
.
I'm thinking if it's possible to monitor exactly what happened while running the a.out
. For example, I want to know exactly how many bytes are used for a.out
, what is happening in each cell memory (8-bit) used by a.out
etc.
Well, I just want to get a stuff like this:
at this moment, the memory of address 0X00001234 is storing 00001001;
at the next moment, the memory of address 0X00001236 is putting its value to cache...
It sounds like using GDB to execute step by step. But for me, I have only an executable binary. I need a way to test it, instead of debugging.
perf mem
maybe, orrr
, or a recording emulator (QEMU in tracing mode)... (Just passing by, if no one else gets rounds to it I’ll write something up in more detail later.) – Stephen Kitt Jan 25 '18 at 16:33rr
? – Rui F Ribeiro Jan 26 '18 at 12:13rr
web site — available asrr
in Debian & co. (Guess who packages it...) – Stephen Kitt Jan 26 '18 at 12:27