On Saturday 15 March 2008 13:57:41 Peter Gibbs wrote:
> Since the valgrind client requests are supposed to be very low overhead
> when not running under valgrind, there should be no problem with adding
> a configure step to define it (and set the correct library path, which I
> just hardcoded), bu
- Original Message -
From: "chromatic" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, March 15, 2008 8:58 PM
Subject: Re: [svn:parrot] r26390 - trunk/src
On Saturday 15 March 2008 05:48:09 [EMAIL PROTECTED] wrote:
New Revision: 26390
Modified:
- Original Message -
From: "chromatic" <[EMAIL PROTECTED]>
Sent: Saturday, March 15, 2008 10:45 PM
On Saturday 15 March 2008 13:40:13 Peter Gibbs wrote:
Incidentally, I found the following useful to stop valgrind
complaining
about uninitialized values causes by walking the stack:
On Saturday 15 March 2008 13:40:13 Peter Gibbs wrote:
> I thought the same thing, but decided some sort of defensive check was
> required anyway, and I got lost trying to track it further. It served my
> purpose at the time, which was to resolve a very fragile bug that moved
> or disappeared while
On Saturday 15 March 2008 05:48:09 [EMAIL PROTECTED] wrote:
> Author: petergibbs
> Date: Sat Mar 15 05:48:08 2008
> New Revision: 26390
>
> Modified:
>trunk/src/inter_call.c
>
> Log:
> Prevent overrun of array. Found using valgrind while chasing down tcl test
> failures on linux x86-64.
>
>
>
