On 29/09/13 12:16, Damien R wrote:
> I am using valgrind 3.7.0 and with the following program, valgrind
> reports no error.
>
> #include <iostream>
>
> struct Foo
> {
> void print()
> {
> std::cout << "foo" << std::endl;
> }
> };
>
> int main()
> {
> Foo * foo = new Foo;
> delete foo;
> foo->print();
> return 0;
> }
>
> Can someone explain why valgrind does not report any error?
Yes. Nothing in the "foo->print()" call actually accesses any memory
that was part of the object.
The body of the function doesn't access any member variables, and it's
not a virtual function so the vtable is not read, so there is no access
to any freed memory.
Tom
--
Tom Hughes (t...@compton.nu)
http://compton.nu/
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
