Ticket #10985: valgrind.log

File valgrind.log, 3.1 KB (added by Levon Gevorgyan, 2 years ago)

valgrind log

Line 
1==68866== Memcheck, a memory error detector
2==68866== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
3==68866== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
4==68866== Command: ffmpeg_g -v 9 -loglevel 99 -i fail.mkv -y -pix_fmt yuv420p10le -c:V libsvtav1 -dolbyvision 1 av1_fail.mkv
5==68866==
6ffmpeg version git-2024-04-29-08781eb Copyright (c) 2000-2024 the FFmpeg developers
7 built with gcc 12 (Debian 12.2.0-14)
8 configuration: --enable-libsvtav1 --enable-librav1e --enable-libaom --enable-libvmaf --enable-libdav1d --enable-libopus --arch=x86_64 --cpu=native --enable-lto --extra-cflags='-O3 -march=native' --extra-cxxflags='-O3 -march=native' --disable-doc --disable-htmlpages --disable-podpages --disable-txtpages
9 libavutil 59. 16.101 / 59. 16.101
10 libavcodec 61. 5.103 / 61. 5.103
11 libavformat 61. 3.103 / 61. 3.103
12 libavdevice 61. 2.100 / 61. 2.100
13 libavfilter 10. 2.101 / 10. 2.101
14 libswscale 8. 2.100 / 8. 2.100
15 libswresample 5. 2.100 / 5. 2.100
16vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0x7F 0x48 0x7F 0x45 0xFD 0x62 0xF1 0x7F
17vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
18vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
19vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
20==68866== valgrind: Unrecognised instruction at address 0x2e3860.
21==68866== at 0x2E3860: UnknownInlinedFun (ffmpeg_opt.c:1225)
22==68866== by 0x2E3860: main (ffmpeg.c:941)
23==68866== Your program just tried to execute an instruction that Valgrind
24==68866== did not recognise. There are two possible reasons for this.
25==68866== 1. Your program has a bug and erroneously jumped to a non-code
26==68866== location. If you are running Memcheck and you just saw a
27==68866== warning about a bad jump, it's probably your program's fault.
28==68866== 2. The instruction is legitimate but Valgrind doesn't handle it,
29==68866== i.e. it's Valgrind's fault. If you think this is the case or
30==68866== you are not sure, please let us know and we'll try to fix it.
31==68866== Either way, Valgrind will now raise a SIGILL signal which will
32==68866== probably kill your program.
33==68866==
34==68866== Process terminating with default action of signal 4 (SIGILL)
35==68866== Illegal opcode at address 0x2E3860
36==68866== at 0x2E3860: UnknownInlinedFun (ffmpeg_opt.c:1225)
37==68866== by 0x2E3860: main (ffmpeg.c:941)
38==68866==
39==68866== HEAP SUMMARY:
40==68866== in use at exit: 73,173 bytes in 6 blocks
41==68866== total heap usage: 6 allocs, 0 frees, 73,173 bytes allocated
42==68866==
43==68866== LEAK SUMMARY:
44==68866== definitely lost: 0 bytes in 0 blocks
45==68866== indirectly lost: 0 bytes in 0 blocks
46==68866== possibly lost: 0 bytes in 0 blocks
47==68866== still reachable: 73,173 bytes in 6 blocks
48==68866== suppressed: 0 bytes in 0 blocks
49==68866== Rerun with --leak-check=full to see details of leaked memory
50==68866==
51==68866== For lists of detected and suppressed errors, rerun with: -s
52==68866== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)