Package: valgrind
Version: 1:3.19.0-1
Severity: normal
Hi!
On any modern mips machine (ie, loongson -- at least as our infra is
concerned; CIP United is rumoured to disagree), valgrind crashes with:
.----
VEX: Unsupported baseline
Found: Loongson-baseline
Cannot continue. Good-bye
vex storage: T total 0 bytes allocated
vex storage: P total 0 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
==1833049== at 0x5804FB44: ??? (in
/usr/libexec/valgrind/memcheck-mips32-linux)
==1833049== by 0x5804FA2C: ??? (in
/usr/libexec/valgrind/memcheck-mips32-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 1833049)
==1833049== at 0x401B920: __start (in /lib/mipsel-linux-gnu/ld.so.1)
==1833049== by 0x7EB7B088: ???
client stack range: [0x7EB78000 0x7EB7BFFF] client SP: 0x7EB7B090
valgrind stack range: [0x42878000 0x42977FFF] top usage: 5512 of 1048576
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.
`----
