From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 6ADD3B707B for ; Fri, 31 Jul 2009 18:02:09 +1000 (EST) Received: from smtp-vbr17.xs4all.nl (smtp-vbr17.xs4all.nl [194.109.24.37]) by ozlabs.org (Postfix) with ESMTP id 9C349DDD1B for ; Fri, 31 Jul 2009 18:02:07 +1000 (EST) Message-ID: <4A72A4E5.1000301@aimvalley.nl> Date: Fri, 31 Jul 2009 10:01:41 +0200 From: Norbert van Bolhuis MIME-Version: 1.0 To: linuxppc-dev@ozlabs.org Subject: Re: can the kernel show user task stack backtrace ? References: <4A71C04E.6060506@aimvalley.nl> <20090730161941.GA14988@mail.gnudd.com> <20090730165555.GA5476@opentech.at> In-Reply-To: <20090730165555.GA5476@opentech.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Cc: Nicholas Mc Guire , Alessandro Rubini List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Thanks for the answers! libSegFault.so seems to do what I want. I'll replace sysctl -w kernel.print-fatal-signals=1 with export LD_PRELOAD=/lib/libSegFault.so since it better suits my needs.