Re: [Valgrind-users] Memcheck and lost pointer tracking

2009-05-08 Thread Theodoros V. Kalamatianos
On Fri, 8 May 2009, Julian Seward wrote: > I'm not convinced it's really possible. The basic problem is that, due > to how the compiler generates code, the last pointer to a block can be > overwritten at some place which is arbitrarily far away (but in the same > procedure) from where it is ov

Re: [Valgrind-users] Memcheck and lost pointer tracking

2009-05-08 Thread Julian Seward
On Friday 08 May 2009, Theodoros V. Kalamatianos wrote: > On Fri, 8 May 2009, Nicholas Nethercote wrote: > > This paper is related too: > > > >author = {Jonas Maebe and Michiel Ronsse and Koen De Bosschere}, > >title = {Precise detection of memory leaks}, > >booktitle = {Pr

Re: [Valgrind-users] Memcheck and lost pointer tracking

2009-05-07 Thread Nicholas Nethercote
On Fri, May 8, 2009 at 3:06 PM, Theodoros V. Kalamatianos wrote: >> >> In general, what you are proposing is possible, but it's not easy, is >> really slow and would be lots of extra code in Memcheck. > > What if it was done in two passes? Run memcheck normally, and then re-run > valgrind repeated

Re: [Valgrind-users] Memcheck and lost pointer tracking

2009-05-07 Thread Theodoros V. Kalamatianos
On Fri, 8 May 2009, Nicholas Nethercote wrote: > This paper is related too: > >author = {Jonas Maebe and Michiel Ronsse and Koen De Bosschere}, >title = {Precise detection of memory leaks}, >booktitle = {Proceedings of the Second International Workshop on Dynamic >

Re: [Valgrind-users] Memcheck and lost pointer tracking

2009-05-07 Thread Theodoros V. Kalamatianos
On Thu, 7 May 2009, John Reiser wrote: >> - The last place where a pointer to a block was clobbered/lost, which >> is a probable location for the actual leak > > Search the Web for "valgrind omega". Ouch, it's even in the valgrind distribution, although disabled by default and undocumented in t

Re: [Valgrind-users] Memcheck and lost pointer tracking

2009-05-07 Thread Nicholas Nethercote
On Fri, May 8, 2009 at 12:49 AM, John Reiser wrote: >> - The last place where a pointer to a block was clobbered/lost, which is a >> probable location for the actual leak > > Search the Web for "valgrind omega". This paper is related too: author = {Jonas Maebe and Michiel Ronsse and Koe

Re: [Valgrind-users] Memcheck and lost pointer tracking

2009-05-07 Thread John Reiser
> - The last place where a pointer to a block was clobbered/lost, which is a > probable location for the actual leak Search the Web for "valgrind omega". -- -- The NEW KODAK i700 Series Scanners deliver under ANY circu

[Valgrind-users] Memcheck and lost pointer tracking

2009-05-06 Thread Theodoros V. Kalamatianos
Hi, I apologise beforehand if this has been discussed before, but in the list archives I only found a 2005 2-message thread that went nowhere. I do not have any experience with the Valgrind code, so if I sound ignorant it's probably because I am :-) I just spent two days trying to find a memo