|
From: Dennis L. <pla...@in...> - 2005-07-22 10:44:41
|
Hi, Hm, I really dont understand the problem with the current format. Valgrind displays the occurence and failure (in this case an invalid read) and after that the memory location where it was allocated and where the access was (or just the address if the address isnt mallocd or stacked). Thats the format for all valgrind messages. Theyre both clearly in one block, indicated through indentation and blank lines between them. For those to whom this format isnt intuitive, its clearly documented in the manual.html... greets Dennis At 10:02 22.07.2005, Christoph Bartoschek wrote: > > ==23198== Invalid read of size 8 > > ==23198== Address 0x140EF0FCE020 is 16 bytes inside a block of size 22 >alloc'd > >Everyone I showed valgrind had a problem understanding this error message and >especially the two tracebacks. Maybe it is possible to simplify this >message. My suggestion would be: > > >Invalid read of size 8 starting at address 0x140EF0FCE020 ><Traceback1> > >Address 0x140EF0FCE020 is 16 bytes inside a block of size 22 ><Traceback2> > >here the address is the link between both messages. One could think of >additional hints for the user. However this goes at the cost of brevity. > >Christoph Bartoschek Carpe quod tibi datum est |