Hi Philippe,
> Also, have you upgraded to 3.12, as suggested by John ?
Yes,I updated to 3.12 - could not see any difference to 3.11.
> Also, try with --read-inline-info=no
All the tests I did now (and the backtraces below) are done with this option
now -- does not seem to make any difference.
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 valgri
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 /path/to/the/smallest/program/which/fails
> 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
Hi,
I have an embedded linux system similar to the BeagleBone. It runs buildroot on
it.
# uname -a
Linux xenon 4.4.21 #1 PREEMPT Thu Dec 8 12:19:53 CET 2016 armv7l GNU/Linux
Within the last days, I enabled valgrind in buildroot (version 3.11.0) to
examine memory issues in some programs.
