Date: Mon, 7 May 2012 10:18:12 -0400 From: "Steve Wills" <swills@FreeBSD.org> To: davidxu@FreeBSD.org Cc: bf1783@gmail.com, freebsd-current@FreeBSD.org, kib@FreeBSD.org, "b. f." <bf1783@googlemail.com> Subject: Re: ctfmerge core dump Message-ID: <d5d975e08424161e16b594f521b73c1d.squirrel@mouf.net> In-Reply-To: <4FA708DA.2010704@gmail.com> References: <CAGFTUwOX1bM1i1a6e1c3AgpV0KCfbc7gbvkdRLq4MwdZ6QnY9A@mail.gmail.com> <4FA58672.1040201@FreeBSD.org> <CAGFTUwOCGURAHUwa=xYAMj6Yf=MkQ=7cG=gGOJ0tYLqEZMkk3A@mail.gmail.com> <4FA708DA.2010704@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 2012/5/6 5:08, b. f. wrote: >> On 5/5/12, Steve Wills<swills@freebsd.org> wrote: >>> Thanks for the info. I took a look at the dump and see this: >>> >>> % sudo gdb /usr/bin/ctfmerge ctfmerge.core >>> [GDB will not be able to debug user-mode threads: Undefined symbol >>> "td_thr_getxmmregs"] > > Hmm, is the thread debugging broken on amd64 now ? td_thr_getxmmregs > resides > in libthread_db and /usr/src/gnu/usr.bin/gdb/libgdb is complaining about > the missing > symbol. > Maybe or maybe I have done something wrong on my system. FWIW, I do all my builds with debugging enabled. BTW, just to confirm, I was able to work around the original issue once I updated past r235068. I had to disable DTrace build and build and install a new libthr, then was able to re-enable DTrace and everything was fine. Thanks, Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d5d975e08424161e16b594f521b73c1d.squirrel>