Hello every one, I am interested on doing program profiling. Lackey was my start point, but I see some limitation that I want to overcome. I need guidance!!!
First, Lackey counts loads, stores, and alu ops, differentiated by IR types; I wonder how I can get more details about i.e. ALU operations (for example: add, mult, div, etc.). BTW, if I am working with the valgrind's IR, can I profile the binary code? Valgrind's IR is machine independent? so can I profile a binary code that in essence is machine dependent? Second, the memory map (stack - heap - data - code). In Lackey, I can trace all the memory references. I know that the address is a virtual address; however, I wonder if there is a memory map - for example, segment code starts at 0x100000, stack starts at 0x800000, and so on. My idea is to profile all data memory accesses - data access from data segment, stack, or heap. Third, system call arguments. I also want to profile system calls. I want to collect information about the arguments (syscall-ID, and parameters). In Valgrind's IR represtation, are the system all arguments passed using the register files or using the stack? If the arguments are passed using the stack, each argument has a memory location; however, the number of arguments depend on the system call. Where I can find more details about system call, and how Valgrind handles them? I will appreciate if someone can point me out what documentation read, what function or tool I can use, etc. Thanks in advance, -- Juan Carlos ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
