You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
could you do something like colour coding data based on functions/areas of code, and dynamically changing the colour coding with reference to debug information.
eg..imagine it knows the current function you're looking at in an editor, you could colour code all the data written, read by that, then colour code other related data (& functions) complimentary to that. drill down and see everything written by a specific line etc..
The text was updated successfully, but these errors were encountered:
To color based on the function that accessed the memory, it would be necessary to increase the size of the sample returned by valgrind so that it also contains the function address - which would decrease performance a little (the sample size would increase from 8 to 16 bytes to store the instruction address as well as the accessed memory address). This should be easy to do with the stack trace samples, though.
That's a good idea to have a way to visualize the memory accessed by a particular line of code, though it would be a bit of work since it would need a new data structure to store this information. Also what would happen if the same memory address were touched by multiple instructions or functions - currently I'm only maintaining one sample per memory address.
could you do something like colour coding data based on functions/areas of code, and dynamically changing the colour coding with reference to debug information.
eg..imagine it knows the current function you're looking at in an editor, you could colour code all the data written, read by that, then colour code other related data (& functions) complimentary to that. drill down and see everything written by a specific line etc..
The text was updated successfully, but these errors were encountered: