Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

colour coding #5

Open
dobkeratops opened this issue Jan 1, 2015 · 1 comment
Open

colour coding #5

dobkeratops opened this issue Jan 1, 2015 · 1 comment

Comments

@dobkeratops
Copy link

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..

@ajclinto
Copy link
Owner

ajclinto commented Jan 2, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants