[Valgrind-users] Reachable blocks after an exit() are unreachable after a return() from main.

[Nicolas W. <nic...@gm...>]

Dear all,

I'm not sure if this is normal behaviour, since I only started using
valgrind today. I've not found anything concerning this on the faq, so I
thought I'd send an email.

The program I'm looking at creates and object (which allocates and deletes
its own memory), in main.
When I run valgrind, and main exits via an exit(0) command, I get quite a
few reachable blocks; some things are vectors declared in main, and one is
memory that's not freed from the object I mentioned.

However, if I change the exit(0) to a return, then the list of still
reachable memory drops to zero.

Is this normal? I thought an exit call was supposed to clear up all memory?

Thanks!

Nick