Valgrind legitimate "possibly lost" bytes example
===

I saw that valgrind classifies memory leaks into:

 - definitely lost
 - indirectly lost
 - **possibly lost**
 - still reachable
 - suppressed

I just fixed a leak where the "possibly lost" was the main problem.

The [documentation says][1]: "***possibly lost** means your program is leaking memory, unless you're doing unusual things with pointers that could cause them to point into the middle of an allocated block; see the user manual for some possible causes*"

May I please know an example of "*doing unusual things with pointers that could cause them to point into the middle of an allocated block*" ?

I mean an example where "possibly lost" can be ignored although it is reported by valgrind. An example in which the use of pointers makes valgrind complain but at the same time the use of the pointers in that way is somehow legitimate

Thank you

  [1]: http://valgrind.org/docs/manual/faq.html#faq.deflost