Date: Thu, 12 Feb 2026 16:28:51 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 293141] Quitting gdb while debugging a program using kqueue leaves system unresponsive Message-ID: <bug-293141-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=293141 Bug ID: 293141 Summary: Quitting gdb while debugging a program using kqueue leaves system unresponsive Product: Base System Version: 14.3-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: brian90013@gmail.com Attachment #268006 text/plain mime type: Created attachment 268006 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=268006&action=edit demonstration code Hello, A single-threaded process that creates two independent kqueue() objects, each with an EVFILT_TIMER event, will cause a hard kernel lockup when run in a debugger (gdb or lldb), interrupted, then exiting the debugger. I am seeing this on amd64 and arm64, FreeBSD 14.3 and 15.0. I do not need root access. To reproduce (using the attached test.c): gcc -O0 -g -o test test.c gdb ./test > r Ctrl + C to interrupt > q Debugger will ask if you are sure you want to quit (y/N) - answer y At this point the system locks up hard (to the point where, when running under vmware or qemu, the vm cannot be shutdown gracefully and the vm container must be killed). I can still ping the box but attempts to ssh in fail. Running shutdown on the console also fails. -- 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-293141-227>