On Tue, Mar 19 2019, Philippe Waroquiers wrote:
>> ==19253==by 0x580A524B: ??? (in
>> /usr/lib/x86_64-linux-gnu/valgrind/memcheck-amd64-linux)
>> ==19253==by 0x580A71EF: ??? (in
>> /usr/lib/x86_64-linux-gnu/valgrind/memcheck-amd64-linux)
>> ==19253==by 0x580F5D80: ??? (in
>> /usr/lib
On Tue, 2019-03-19 at 19:05 +0100, Yuri D'Elia wrote:
> Hi everyone. It looks like the impossible happened. I was attempting to
> blindly run valgrind on debian unstable against slic3r-pe (mostly c++,
> which itself uses wxWidgets 3.1), both freshly compiled using gcc 8.3
> and got the following:
>
Some more info is needed to guess what the problem
could be.
Debug your program when running under valgrind using
gdb + vgdb.
Compare the behaviour e.g. with gdb+vgdb between the non working
system and a working system
and/or compare the -v -v -v -d -d -d traces.
Philippe
On Tue, 2019-03-19
Hi everyone. It looks like the impossible happened. I was attempting to
blindly run valgrind on debian unstable against slic3r-pe (mostly c++,
which itself uses wxWidgets 3.1), both freshly compiled using gcc 8.3
and got the following:
$ valgrind ./src/slic3r-gui
==19253== Memcheck, a memory error
Also, FWIW, I tried the rh devtoolset version, 3.14 compiled by myself
and the git version, all behave the same way.
On 3/19/19 9:42 AM, Matthew Bettencourt via Valgrind-users wrote:
When I run a real program valgrind hangs on my redhat desktop, however
I can run on other systems with the same
When I run a real program valgrind hangs on my redhat desktop, however I
can run on other systems with the same executable.
I ran
valgrind -v -v -v -d -d -d myprog.exe
and it spits out a lot of output and then sits there for many minutes,
I've let it sit for overnight and no progress.
I
