Segfault on some applications using qt5

[BERTRAND Joël]

Conrad Meyer a écrit :
> What version of FreeBSD is this?  When you reproduce the crash, can
> you provide gdb "info locals", "info args", and "info registers" in
> frame 0 context?

	I have tried to obtain these informations. Context: okular provided by
ports and qt5 (5.14.2) built from sources.

(gdb) info locals
No symbol table info available.
(gdb) info args
No symbol table info available.
(gdb) info registers
rax            0x805e65220         34458718752
rbx            0x272               626
rcx            0x805e28000         34458468352
rdx            0x3d220             250400
rsi            0x3d220             250400
rdi            0x805e28000         34458468352
rbp            0x7fffffffcc30      0x7fffffffcc30
rsp            0x7fffffffcc30      0x7fffffffcc30
r8             0xff000000          4278190080
r9             0xef                239
r10            0x801872850         34385373264
r11            0x0                 0
r12            0x80403c700         34427094784
r13            0x0                 0
r14            0x64                100
r15            0x0                 0
rip            0x80163fa20         0x80163fa20
<qt_memfillXX_avx2(unsigned char*, long long __vector(4), long long)+32>
eflags         0x10206             [ PF IF RF ]
cs             0x43                67
ss             0x3b                59
ds             <unavailable>
es             <unavailable>
fs             <unavailable>
gs             <unavailable>
fs_base        0x802ffd8e0         34410060000
gs_base        0x0                 0
(gdb)

	If I try to reproduce this bug with a new qt5 configuration (-no-strip
-no-evdev -no-avx -no-avx2 -no-avx512), okular aborts in the _same_
function (qt_memfillXX_avx2).

	Best regards,

	JKB