Goplat <[EMAIL PROTECTED]> wrote:
> case 1048576:
> /* can't be bothered to calculate larger ones */
Yep. Valgrind always failed here. I did submit several bugfixes. Didn't
receive any answer. Sorry forgot to report, but my valgrind here was
always patched;
+ case 524288:
--- Elizabeth Mattijsen <[EMAIL PROTECTED]> wrote:
> At 18:27 + 2/24/04, Arthur Bergman wrote:
> >Using valgrind 1.9.6 I find it impossible to use with parrot, is
> >this a known issue, should I try and get someone to upgrade valgrind
> >for me?
>
> Current stable is 2.0.0, unstable is 2.1.0
At 18:27 + 2/24/04, Arthur Bergman wrote:
Using valgrind 1.9.6 I find it impossible to use with parrot, is
this a known issue, should I try and get someone to upgrade valgrind
for me?
Current stable is 2.0.0, unstable is 2.1.0. I would think an update
would be in order before send in bug re
Using valgrind 1.9.6 I find it impossible to use with parrot, is this a
known issue, should I try and get someone to upgrade valgrind for me?
The following impossible happens.
switch% valgrind --num-callers=100 ./parrot examples/assembly/mops.pasm
==23809== Memcheck, a.k.a. Valgrind, a memory er
