Date: Wed, 23 Jul 2008 15:01:24 -0500 (CDT) From: "Sean C. Farley" <scf@FreeBSD.org> To: Roman Divacky <rdivacky@FreeBSD.org> Cc: freebsd-emulation@FreeBSD.org Subject: Re: kern/122318 (CMake core dumping, chroot exiting) Message-ID: <alpine.BSF.1.10.0807231459030.12600@thor.farley.org> In-Reply-To: <20080723184450.GA25356@freebsd.org> References: <alpine.BSF.1.10.0807231236140.12600@thor.farley.org> <20080723184450.GA25356@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 23 Jul 2008, Roman Divacky wrote: > On Wed, Jul 23, 2008 at 12:50:51PM -0500, Sean C. Farley wrote: >> I am seeing if anyone has any insight on this PR (kern/122318[1]). >> It would be nice to once again build using cmake within a Linux >> chroot. :) >> >> Basically, the bug is that not only that cmake is dumping core; it is >> also forcing the user out of the chroot environment. Here is the >> command used to start the chroot: >> /compat/linux/usr/sbin/chroot <chroot path> su - <build user> >> >> 1. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/122318 > > looking at the trace you provided I guess this is what's going on: > > cmake forks/execs gcc and waits to be notified about the success of > the command it tried, the notification comes (the SIGCHLD) the handler > tries do something and then returns and now something is wrong and it > receives the SIGSEGV.. > > or am I wrong and linux_ktrace does not translate signals and the > SIGCHLD is in fact SIGTSTP? > > what is the fd 3 and 4? can you provide full ktrace.out? I have the full output of the execution here using ktrace -d: http://www.farley.org/freebsd/tmp/cmake-kdump.txt Sean -- scf@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.1.10.0807231459030.12600>