On Wed, Jul 16, 2014 at 2:58 PM, John Peterson <[email protected]> wrote:
> On Wed, Jul 16, 2014 at 2:31 PM, John Peterson <[email protected]> wrote:
>> On Wed, Jul 16, 2014 at 1:39 PM, John Peterson <[email protected]> wrote:
>>> On Wed, Jul 16, 2014 at 1:33 PM, Kirk, Benjamin (JSC-EG311)
>>> <[email protected]> wrote:
>>>>
>>>> should be fixed in valgrind 3.9.0.  What version are you running?
>>>
>>> 3.7.0, I could try and see if there is a newer binary available for
>>> the system I'm on.
>>
>> FYI, built 3.9.0 from source, same error as in 3.7.0.
>
> Just pushed the commit below.  It doesn't fix the valgrind error, but
> definitely seems wrong.  Actually not sure how it compiled...
>
> https://github.com/libMesh/libmesh/commit/49a181db4742e4b4458e024d9e1fa152278cfeca

Looks like that bug was introduced here:

https://github.com/libMesh/libmesh/commit/64715adf2018d4b78df559c9c7dd8e2c2d00e55d

-- 
John

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to