Date: Mon, 08 Feb 2021 01:35:44 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 253318] lldb: aborted when debugging named Message-ID: <bug-253318-227-vsDVMr61s0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-253318-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=253318 --- Comment #3 from Xin LI <delphij@FreeBSD.org> --- It would take about a day for me to catch the offending program (more context at https://gitlab.isc.org/isc-projects/bind9/-/issues/2465 if you are interested) to enter the state that I need to debug, so it would take some time for me to try to reproduce the lldb issue. What I did was fairly basic, basically I have a runaway BIND instance, which after receiving a SIGTERM won't exit, and I was attaching to the process and trying to get a backtrace for all threads. Or in other words, I did: sudo lldb --attach-pid `pgrep named` `which named` and were going to do a "thread backtrace all", while doing that I might have pressed <tab> and lldb dumped core. === Should I build a lldb version with -g and -O0 just in case, by the way? -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-253318-227-vsDVMr61s0>