Attachment 1451010 Details for Bug 1464211 – valgrind output

valgrind output

valgrind-output.txt (text/plain), 4.10 KB, created by Rob Clark on 2018-06-13 19:36:52 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Rob Clark

Created: 2018-06-13 19:36:52 UTC

Size: 4.10 KB

patch

obsolete

>==32073== Memcheck, a memory error detector
>==32073== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
>==32073== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright info
>==32073== Command: ./deqp-gles31 --deqp-visibility=hidden --deqp-case=dEQP-GLES31.functional.ssbo.layout.random.arrays_of_arrays.1 --deqp-log-filename=results/dEQP-GLES31.functional.ssbo.layout.random.arrays_of_arrays.1.qpa
>==32073== 
>ARM64 front end: branch_etc
>disInstr(arm64): unhandled instruction 0xD5380000
>disInstr(arm64): 1101'0101 0011'1000 0000'0000 0000'0000
>==32073== valgrind: Unrecognised instruction at address 0x40150cc.
>==32073==    at 0x40150CC: init_cpu_features (cpu-features.c:72)
>==32073==    by 0x40150CC: dl_platform_init (dl-machine.h:208)
>==32073==    by 0x40150CC: _dl_sysdep_start (dl-sysdep.c:231)
>==32073==    by 0x40018C3: _dl_start_final (rtld.c:411)
>==32073==    by 0x4001B3F: _dl_start (rtld.c:520)
>==32073==    by 0x4001047: ??? (in /usr/lib64/ld-2.27.9000.so)
>==32073== Your program just tried to execute an instruction that Valgrind
>==32073== did not recognise.  There are two possible reasons for this.
>==32073== 1. Your program has a bug and erroneously jumped to a non-code
>==32073==    location.  If you are running Memcheck and you just saw a
>==32073==    warning about a bad jump, it's probably your program's fault.
>==32073== 2. The instruction is legitimate but Valgrind doesn't handle it,
>==32073==    i.e. it's Valgrind's fault.  If you think this is the case or
>==32073==    you are not sure, please let us know and we'll try to fix it.
>==32073== Either way, Valgrind will now raise a SIGILL signal which will
>==32073== probably kill your program.
>==32073== 
>==32073== Process terminating with default action of signal 4 (SIGILL): dumping core
>==32073==  Illegal opcode at address 0x40150CC
>==32073==    at 0x40150CC: init_cpu_features (cpu-features.c:72)
>==32073==    by 0x40150CC: dl_platform_init (dl-machine.h:208)
>==32073==    by 0x40150CC: _dl_sysdep_start (dl-sysdep.c:231)
>==32073==    by 0x40018C3: _dl_start_final (rtld.c:411)
>==32073==    by 0x4001B3F: _dl_start (rtld.c:520)
>==32073==    by 0x4001047: ??? (in /usr/lib64/ld-2.27.9000.so)
>
>valgrind: m_coredump/coredump-elf.c:506 (fill_fpu): Assertion 'Unimplemented functionality' failed.
>valgrind: valgrind
>
>host stacktrace:
>==32073==    at 0x3803E0FC: show_sched_status_wrk (m_libcassert.c:378)
>==32073==    by 0x3803E22B: report_and_quit (m_libcassert.c:449)
>==32073==    by 0x3803E387: vgPlain_assert_fail (m_libcassert.c:515)
>==32073==    by 0x380706FB: fill_fpu.isra.4 (coredump-elf.c:506)
>==32073==    by 0x380708CF: dump_one_thread (coredump-elf.c:563)
>==32073==    by 0x380708CF: make_elf_coredump (coredump-elf.c:667)
>==32073==    by 0x380708CF: vgPlain_make_coredump (coredump-elf.c:748)
>==32073==    by 0x3805654F: default_action (m_signals.c:1937)
>==32073==    by 0x3805654F: deliver_signal (m_signals.c:1997)
>==32073==    by 0x38056D0B: vgPlain_synth_sigill (m_signals.c:2106)
>==32073==    by 0x380982DB: vgPlain_scheduler (scheduler.c:1577)
>==32073==    by 0x380A939F: thread_wrapper (syswrap-linux.c:103)
>==32073==    by 0x380A939F: run_a_thread_NORETURN (syswrap-linux.c:156)
>==32073==    by 0xFFFFFFFFFFFFFFFF: ???
>
>sched status:
>  running_tid=1
>
>Thread 1: status = VgTs_Runnable (lwpid 32073)
>==32073==    at 0x40150CC: init_cpu_features (cpu-features.c:72)
>==32073==    by 0x40150CC: dl_platform_init (dl-machine.h:208)
>==32073==    by 0x40150CC: _dl_sysdep_start (dl-sysdep.c:231)
>==32073==    by 0x40018C3: _dl_start_final (rtld.c:411)
>==32073==    by 0x4001B3F: _dl_start (rtld.c:520)
>==32073==    by 0x4001047: ??? (in /usr/lib64/ld-2.27.9000.so)
>
>
>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.
>

Actions: View

Attachments on bug 1464211: 1451010