y local copy of valgrind
> (actually just tracking a single address, and printing out one - even
> when multiple copies were leaked). Unfortunately, I've since lost that
> patch. Fortunately, it was really simple - so doing something like
> that yourself shouldn't be hard.
>
&g
Hi all,
I am trying to find a well-hidden memory leak. To do so, it would be
immensely useful to know the memory addresses of the leaked objects.
Is there any way I can tell valgrind to show the addresses in its
memory leak output (just like it does e.g. on access violations)?
Thanks,
Rainer
---
Hi all,
I am working with the svn version of valgrind (updated this morning).
I see a series of violations in drd which I can not identify the root
cause. An example violation looks like this:
==22593== Thread 3:
==22593== Conflicting load by thread 3 at 0x3401e1b328 size 4
==22593==at 0x3401
On Wed, Mar 17, 2010 at 11:26 PM, Julian Seward wrote:
> These are likely to be stuff which you can't fix by adding function
> replacements. So you'll have to suppress them. I can't say whether
> they are false errors or not (probably are).
OK, thanks. I'll take the supression path.
Attached i
On Wed, Mar 17, 2010 at 6:35 PM, Tim Post wrote:
> On Wed, 2010-03-17 at 15:34 +0100, Rainer Gerhards wrote:
>> ==11294== Address 0x7a29228 is 47836712 bytes after the accessing
>> pointer's
>> ==11294== legitimate range, a block of size 288 alloc'd
>
> Did
On Wed, Mar 17, 2010 at 11:20 AM, Julian Seward wrote:
> Hmm, you'll need to create a STRNCMP template in h_intercepts.c do deal
> with that. You can just copy the relevant code from mc_replace_strmem.c.
>
> If you do this and it works, please send the resulting diff.
This seems to work :) Befor
On Tue, Mar 16, 2010 at 7:29 PM, Julian Seward wrote:
> I suggest you try the svn trunk valgrind. I put in some automatic
> replacements for strchr and some related ones (see h_intercepts.c)
> and so you should not see these complaints any more. Build details
> are at http://www.valgrind.org/dow
Hi all,
I am trying to solve some hard-to-find issue with valgrind (which I
use regularly and is a great tool, BTW :)). As memcheck does not find
anything, I gave exp-ptrcheck a try.
While the program is memcheck-clean, I get lots of violations and have
not yet managed to find any failure in my c
which compilers.
So... sorry for the disturbance.
Rainer
On Thu, Jan 29, 2009 at 11:56 AM, Julian Seward wrote:
> On Thursday 29 January 2009, Bart Van Assche wrote:
>> On Thu, Jan 29, 2009 at 11:10 AM, Rainer Gerhards
> wrote:
>> > well, I have never tried to verify it wit
In the light of this and Julian's post, my practical experience may
simply be a result of deadlocks that arise when the stdio library does
its looking and my non-aware app does not include this into its
looking scenario. Probably these deadlocks lead me to try valgrind to
fix it, where the messages
y 2009, Rainer Gerhards wrote:
>
>> The standard io library is not thread safe.
>
> Are you sure about that?
>
> http://www.unix.org/whitepapers/reentrant.html:
>
> The POSIX.1 and C-language functions that operate on character
> streams (represented by pointers to o
On Thu, Jan 29, 2009 at 9:58 AM, jody wrote:
> Hi
> I tried out DRD, but even though i read the DRD manual,
> i don't really understand the output (i used --tool=drd --var-info=yes -v)
> I get many messages concerning the same line, a print statement
> performed by the thread just before it exits
Hi folks,
I just wanted to share my story on how valgrind helped my solve a hard
to track threading issue. The story is actually an analysis of said
issue and covers how valgrind helped solve it but also includes
information on where I screwed up. I think it may be entertaining,
maybe even useful,
I agree to these comments, but would also recommend to not *only* use
helgrind but also the new DRD tool. DRD did an excellent job for my
project. The newest release now contains a stable release.
Just my 2cts...
Rainer
On Wed, Jan 28, 2009 at 6:44 PM, Julian Seward wrote:
>
>> I have a server
I don't know if that is possible, but you could write a supression
file for those "known" memory leaks. valgrind can even create this
file for you. I don't remember the exact procedure, but it is either
in the valgrind faq or manual.
HTH
Rainer
On Tue, Nov 25, 2008 at 12:41 PM, DexterMagnific <[E
15 matches
Mail list logo
