# Valgrind: what is the difference between a store and a modify? [closed]

I am using the Vlagrind lackey tool to examine the full memory reference string of a running computer program and wonder what the difference between a "store" and a "modify" might be - and do these differences reflect a real difference in category of memory manipulation, or are they merely a convenience for the user/programmer of Valgrind's lackey tool?

The comments on the lk_main.c source code give these examples of (a) A store:

movl %eax, (%ebx)


And (b) a modify

incl (%ecx)


I appreciate this is a question about a specific piece of software, but what I really want to know is if it is valid to consider stores and modifies as, in effect "stores" - as much texts on memory seem to regard the two basic operations as load (read) and store (write).

## closed as off-topic by Raphael♦Nov 2 '13 at 15:44

This question appears to be off-topic. The users who voted to close gave this specific reason:

• "Questions about software development or programming tools are off-topic here, but can be asked on Stack Overflow." – Raphael
If this question can be reworded to fit the rules in the help center, please edit the question.