|
From: Philippe W. <phi...@sk...> - 2019-05-12 15:31:38
|
Currently, when a block is described (e.g. in an error message), valgrind pub_tool_addrinfo.h VG_(pp_addrinfo) and VG_(pp_addrinfo_mc) do not print the block address. At work, I received some suggestions that adding the block address will improve the block descriptions and error messages. It will e.g. help to make the offset given in the error message more clear. Also, giving the block address can be useful to link with application trace of allocated memory. Currently, in an error, valgrind outputs a description such as: ==18039== Address 0x51d8048 is 8 bytes inside a block of size 15 alloc'd ==18039== at 0x4C2BF3D: malloc (vg_replace_malloc.c:309) ==18039== by 0x108751: main (badpoll.c:12) Here follows some possible ways to show the block address in the first line: ==18039== Address 0x51d8048 is 8 bytes inside a block (0x51d8040) of size 15 alloc'd ==18039== Address 0x51d8048 is 8 bytes inside a block at 0x51d8040 of size 15 alloc'd ==18039== Address 0x51d8048 is 8 bytes inside a block address 0x51d8040 of size 15 alloc'd Feedback ? Other suggestions ? Thanks Philippe |