Re: [Valgrind-users] Valgrind crash on armv7l

2017-01-04 Thread Philippe Waroquiers
On Wed, 2017-01-04 at 13:43 +0100, frank_w...@web.de wrote: > Happy new year! > > > Am 08.12.2016 14:34 schrieb John Reiser: > > [...] > > Most of the time? Then run valgrind under gdb, get the traceback > > at the time of the SIGSEGV, and file a bug report against valgrind. > > $ gdb

Re: [Valgrind-users] Valgrind crash on armv7l

2017-01-04 Thread Frank_wtal
Happy new year! Am 08.12.2016 14:34 schrieb John Reiser: > [...] > Most of the time?  Then run valgrind under gdb, get the traceback > at the time of the SIGSEGV, and file a bug report against valgrind. >     $ gdb valgrind >     (gdb) run --tool=memcheck

Re: [Valgrind-users] Valgrind crash on armv7l

2016-12-08 Thread John Reiser
> Most of the time, when I start valgrind like this: > # valgrind --tool=memcheck > it exits with a segmentation fault. I tried different programs, small and > big, but this does not really seem to make a difference. ... Most of the time? Then run valgrind under gdb, get the traceback at the