On 03.09.2014 21:56, Philippe Waroquiers wrote:
> On Wed, 2014-09-03 at 21:02 +0200, Florian Krohm wrote:
>
>> I reran the regtest and this time the test passed. That does not sound
>> good. Looks like I should run memcheck on helgrind
> I did run the full test suite in an outer memcheck some
On Wed, 2014-09-03 at 21:02 +0200, Florian Krohm wrote:
> I reran the regtest and this time the test passed. That does not sound
> good. Looks like I should run memcheck on helgrind
I did run the full test suite in an outer memcheck some days ago.
Did not find anything wrong; but the difficult
On 03.09.2014 19:02, Florian Krohm wrote:
> On 03.09.2014 13:03, Julian Seward wrote:
>>
>> A beta tarball for 3.10.0 is available now at
>> http://www.valgrind.org/downloads/valgrind-3.10.0.BETA1.tar.bz2
>> (md5sum = dee188c79a9795fee178ba17f42c40b3)
>
> I just tested this on my x86-64. I see one
On 03.09.2014 13:03, Julian Seward wrote:
>
> A beta tarball for 3.10.0 is available now at
> http://www.valgrind.org/downloads/valgrind-3.10.0.BETA1.tar.bz2
> (md5sum = dee188c79a9795fee178ba17f42c40b3)
I just tested this on my x86-64. I see one unexpected failure in the
testsuite:
helgrind/tes
On 09/03/2014 02:47 PM, Phil Longstaff wrote:
> Is more information available about these changes?
> I'd like to see more detail on "improved error messages"
> and "stack traces through inlined function calls".
Sure. Here is the entire NEWS entry for the release so far.
J
Release 3.10.0 (mid S
Is more information available about these changes? I'd like to see more detail
on "improved error messages" and "stack traces through inlined function calls".
-Original Message-
From: Julian Seward [mailto:jsew...@acm.org]
Sent: Wednesday, September 03, 2014 7:04 AM
To: Valgrind-users@l
