Date: Tue, 8 May 2007 07:28:11 -0600 From: John E Hein <jhein@timing.com> To: "Wilkinson, Alex" <alex.wilkinson@dsto.defence.gov.au> Cc: emulation@freebsd.org Subject: Re: sec:uRe: sec:uRe: sec:uRe: [net/citrix_ica/] /usr/local/bin/wfcmgr ... hangs upon exec(). Message-ID: <17984.31467.919324.655183@gromit.timing.com> In-Reply-To: <20070508024404.GE7353@obelix.dsto.defence.gov.au> References: <20070504035455.GA19928@obelix.dsto.defence.gov.au> <20070506132617.GF36879@obelix.dsto.defence.gov.au> <17981.62139.156155.588677@gromit.timing.com> <20070507073010.GG3240@obelix.dsto.defence.gov.au> <20070507095959.lqa9n27yso8cwo4s@webmail.leidinger.net> <20070507080332.GI3240@obelix.dsto.defence.gov.au> <17983.13326.774561.259231@gromit.timing.com> <20070508024404.GE7353@obelix.dsto.defence.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Wilkinson, Alex wrote at 10:44 +0800 on May 8, 2007: > 0n Mon, May 07, 2007 at 08:13:34AM -0600, John E Hein wrote: > > >If you have DEBUG defined when you build linux.ko, then kldload _that_ > >linux.ko, you should immediately be able to see compat.linux.debug in > >the output of sysctl -a. > > > >How about this: > >strings linux.ko | grep Linux.debugging.control > >(make sure this is the linux.ko that you think you are kldload'ing) > > #ls /boot/kernel/*linux* > /boot/kernel/3dfx_linux.ko* /boot/kernel/amr_linux.ko.symbols* > /boot/kernel/3dfx_linux.ko.symbols* /boot/kernel/linux.ko* > /boot/kernel/aac_linux.ko* /boot/kernel/linux.ko.symbols* > /boot/kernel/aac_linux.ko.symbols* /boot/kernel/mfi_linux.ko* > /boot/kernel/amr_linux.ko* /boot/kernel/mfi_linux.ko.symbols* > > #strings /boot/kernel/*linux* | grep Linux.debugging.control > # > > Well I definitely built a new kernel with debugging added to: > /usr/src/sys/modules/linux/Makefile. All this tells me that the linux.ko that is installed in /boot/kernel was not built with -DDEBUG Look at the bottom of linux_mib.c - you should have "Linux debugging control" in linux.ko if built with -DDEBUG. So you either built linux.ko incorrectly or installed it incorrectly (or failed to install it). If you have any further questions about the build/install process, you may want to try freebsd-questions.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17984.31467.919324.655183>