Date: Sat, 25 Nov 2023 06:35:25 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275322] Improper handling of mxcsr register during debug (gdb/lldb) Message-ID: <bug-275322-227-ZKtILxsgDH@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275322-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275322 --- Comment #3 from Konstantin Belousov <kib@FreeBSD.org> --- I cannot reproduce this. For me it looks like this: Breakpoint 1, main (argc=1, argv=0x7fffffffe5f8) at pr275322.c:14 14 in pr275322.c (gdb) c Continuing. pid 99860 comm pr275322: signal 5 err 0 code 2 type 10 addr 0x201703 rsp 0x7fffffffe540 rip 0x201703 rax 0<8b 45 ec 89 04 25 30 3a> pid 99860 comm pr275322: signal 5 err 0 code 1 type 3 addr 0x201742 rsp 0x7fffffffe540 rip 0x201742 rax 0x9fc0<44 0f 59 e0 f2 44 0f 11> Breakpoint 2, 0x0000000000201741 in main (argc=1, argv=0x7fffffffe5f8) at pr275322.c:18 18 in pr275322.c (gdb) info registers mxcsr mxcsr 0x9fc0 [ DAZ IM DM ZM OM UM PM FZ ] (gdb) c Continuing. pid 99860 comm pr275322: signal 5 err 0 code 2 type 10 addr 0x201746 rsp 0x7fffffffe540 rip 0x201746 rax 0x9fc0<f2 44 0f 11 24 25 40 3a> ra=7.01209994486364354e-310 reatt=10000000000 ra * reatt-> result =0 savemxcsr 00001f80 mxcsr_set 00009fc0 showmxcsr 00009fc0 mxcsr 00009fc0 [Inferior 1 (process 99860) exited normally] I tried this on two machines, one being KabyLake, and another Goldmont. Are you trying this on bare metal boot? What is the CPU where the problem occurs? -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275322-227-ZKtILxsgDH>