Date: Fri, 09 Dec 2022 14:02:48 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 267606] x11-drivers/xf86-video-nv: Segmentation Fault post update from 1.20.14,1 to 21.1.4 Message-ID: <bug-267606-7141-zRIMFF5nzQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267606-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-267606-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267606 --- Comment #7 from Sergiy <Black_N@ukr.net> --- (In reply to Huskers from comment #6) I tried but I have a problem. It=E2=80=99s my problem. When installing FreeBSD on my Toshiba, I didn't select the necessary debugg= ing components, e.g kernel-dbg - Kernel and modules with debug symbols activated... As a result, to debugging (even with the system hardening turned off) the d= ump of the Xorg.core file formed after the xorg-server crash, in my opinion, do= es not provide the necessary information. In my case, as an option, you can try to install the necessary components in the kernel (bsdinstall), but the problem is that some changes have already taken place in the system - patches that came out p1, p2, p3, p4, p5. I feel insecure... What I did from what I understood. By default, the system has the lldb debugger installed. $ man lldb I tried the following: # lldb -c /path_to_file/Xorg.core in my case: # lldb -c /home/Black_N/Xorg.core if the launch of X took place under root, it is possible: # lldb -c /Xorg.core then you need to run a command for backtrace =E2=80=94 bt An example of what I got: root@T0SHA:/home/Black_N # lldb -c Xorg.core (lldb) target create --core "Xorg.core" Core file '/home/Black_N/Xorg.core' (x86_64) was loaded. (lldb) bt * thread #1, name =3D 'Xorg', stop reason =3D signal SIGABRT * frame #0: 0x00000008293d633a frame #1: 0x000000082934ec74 (lldb) quit command (quit or exit) - to exit the debugger To use the gdb debugger, it must first be installed: # pkg install gdb After installing gdb, a more complete man page for it will be available $ man gdb In my case, the launch is from the user's directory, so I executed/got: # gdb -c Xorg.core GNU gdb (GDB) 12.1 [GDB v12.1 for FreeBSD] Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.htm= l> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd13.1". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". [New LWP 100146] [New LWP 100147] Core was generated by `/usr/local/libexec/Xorg :0 -auth /root/.serverauth.1055'. Program terminated with signal SIGABRT, Aborted. Sent by thr_kill() from pid 1069 and user 0. #0 0x00000008293d633a in ?? () [Current thread is 1 (LWP 100146)] (gdb) bt #0 0x00000008293d633a in ?? () #1 0x000000082934ec74 in ?? () #2 0x0000000000018732 in ?? () #3 0xe0e2e1da422b1897 in ?? () #4 0x0000000820e57fa4 in ?? () #5 0x0000000820e588c0 in ?? () #6 0x0000000820e57fc0 in ?? () #7 0x0000000829400109 in ?? () #8 0xe0e2e1da422b1897 in ?? () #9 0x0000000000000000 in ?? () (gdb) exit But the data is not informative, since the kernel lacks the necessary components... I did this for the first time, sorry, maybe I'm wrong. Related to the topic, there is a newer version of the nv driver on the X.org website, maybe when it is ported, it will also solve our problem www.x.org/releases/individual/driver/ xf86-video-nv-2.1.22 2022-07-27 Sorry for my English. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267606-7141-zRIMFF5nzQ>