valgrind-users

[Valgrind-users] Can i get a warning to issue the stacktrace?

[Dilkie, L. <Lee...@mi...>]

I'm getting a few

"Warning: src and dst overlap in memcpy (0xblah, 0xblah, a_length)"

Is there any way to get valgrind to dump the call stack on this warning like it does on errors so i could see where this is happening?

I'm using the latest version, cvs'ed this morning. It solved the seg fault when i tried to run hellgrind on the "official" version but this new warning message is emitted now.

TIA,

-lee

Re: [Valgrind-users] Can i get a warning to issue the stacktrace?

[Tom H. <th...@cy...>]

In message <29B...@rn...> you wrote:

> I'm getting a few
> 
> "Warning: src and dst overlap in memcpy (0xblah, 0xblah, a_length)"
> 
> Is there any way to get valgrind to dump the call stack on this warning
> like it does on errors so i could see where this is happening?

I happen to have a patch to make it do that that I've been meaning
to send it. I'm attaching it to this message...

Tom

-- 
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/

Re: [Valgrind-users] Can i get a warning to issue the stacktrace?

[Nicholas N. <nj...@ca...>]

On Thu, 1 May 2003, Tom Hughes wrote:

> > I'm getting a few
> >
> > "Warning: src and dst overlap in memcpy (0xblah, 0xblah, a_length)"
> >
> > Is there any way to get valgrind to dump the call stack on this warning
> > like it does on errors so i could see where this is happening?
>
> I happen to have a patch to make it do that that I've been meaning
> to send it. I'm attaching it to this message...

Cool, thanks.  That was on my todo list, you've saved me some time :)
I will commit it some time soon.
(where "two days" < "soon" && "two weeks" < "soon")

N

Re: [Valgrind-users] Can i get a warning to issue the stacktrace?

[Bastien C. <ba...@ch...>]

On Thursday 01 May 2003 22:56, Nicholas Nethercote wrote:
> Cool, thanks.  That was on my todo list, you've saved me some time :)
> I will commit it some time soon.
> (where "two days" < "soon" && "two weeks" < "soon")

Shouldn't that be ... "two weeks" > "soon"? :-)

B.

-- 
        -- The universe has its own cure for stupidity. --
         -- Unfortunately, it doesn't always apply it. --

Re: [Valgrind-users] Can i get a warning to issue the stacktrace?

[Nicholas N. <nj...@ca...>]

On Fri, 2 May 2003, Bastien Chevreux wrote:

> On Thursday 01 May 2003 22:56, Nicholas Nethercote wrote:
> > Cool, thanks.  That was on my todo list, you've saved me some time :)
> > I will commit it some time soon.
> > (where "two days" < "soon" && "two weeks" < "soon")
>
> Shouldn't that be ... "two weeks" > "soon"? :-)

Unless I'm planning on never committing it, a ha ha...

You're right.  Lucky Tom wrote the patch instead of me :)

N

Re: [Valgrind-users] Can i get a warning to issue the stacktrace?

[Nicholas N. <nj...@ca...>]

On Thu, 1 May 2003, Tom Hughes wrote:

> > "Warning: src and dst overlap in memcpy (0xblah, 0xblah, a_length)"
> >
> > Is there any way to get valgrind to dump the call stack on this warning
> > like it does on errors so i could see where this is happening?
>
> I happen to have a patch to make it do that that I've been meaning
> to send it. I'm attaching it to this message...

Committed to CVS HEAD, thanks.

N