SEGFAULT with MM HEAD when probing
bjorn at mork.no
Wed Apr 21 19:59:13 UTC 2021
Aleksander Morgado <aleksander at aleksander.es> writes:
>> Bu can't I just run valgrind on the MIPS CPU? Any hints on how to use
>> valgrind? It's one of those tools I've been thing that I should
>> explore, but never have..
> I have no idea if you can run valgrind on that setup, just give it a
> try maybe? If we're interested in finding invalid read/writes in
> memory (ignoring leaks), the valgrind call would be basically this:
> # G_SLICE=always-malloc valgrind --log-file=valgrind.log
> /usr/sbin/ModemManager --debug
> The valgrind.log file would contain the errors reported.
OK, that seemed too easy. Don't know how to progress here:
root at finn:~# G_SLICE=always-malloc valgrind --log-file=valgrind.log /tmp/ModemManager --debug
More information about the ModemManager-devel