From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753183Ab1A0Txg (ORCPT ); Thu, 27 Jan 2011 14:53:36 -0500 Received: from mail-iy0-f174.google.com ([209.85.210.174]:55477 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751482Ab1A0Txf (ORCPT ); Thu, 27 Jan 2011 14:53:35 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=wc34AXK5ep/Xnc7U2cRvCDPycfvCgT1u4wzyZDhr6+MMje/iQ9cJttZ7egYbAwFQqW rtbZ5aL6kWtKFjPvRHAPd9jv4O0rQ7NCRT2x/gD6PJ6N9klAM5q2//CMyaop8bK/H7tk N7JjCtEn+aUkVfG4Uf5I5CuCHUUEmvUHzuzZs= Date: Thu, 27 Jan 2011 11:53:25 -0800 From: Dmitry Torokhov To: Mark Lord Cc: Mauro Carvalho Chehab , Linus Torvalds , Linux Kernel , linux-input@vger.kernel.org, linux-media@vger.kernel.org Subject: Re: 2.6.36/2.6.37: broken compatibility with userspace input-utils ? Message-ID: <20110127195325.GB29910@core.coreip.homeip.net> References: <4D3F4D11.9040302@teksavvy.com> <20110125232914.GA20130@core.coreip.homeip.net> <20110126020003.GA23085@core.coreip.homeip.net> <4D403855.4050706@teksavvy.com> <4D40C3D7.90608@teksavvy.com> <4D40C551.4020907@teksavvy.com> <20110127021227.GA29709@core.coreip.homeip.net> <4D40E41D.2030003@teksavvy.com> <20110127163931.GA1825@core.coreip.homeip.net> <4D41B5A0.70704@teksavvy.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D41B5A0.70704@teksavvy.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 27, 2011 at 01:12:48PM -0500, Mark Lord wrote: > On 11-01-27 11:39 AM, Dmitry Torokhov wrote: > > On Wed, Jan 26, 2011 at 10:18:53PM -0500, Mark Lord wrote: > >> No, it does not seem to segfault when I unload/reload ir-kbd-i2c > >> and then invoke it by hand with the same parameters. > >> Quite possibly the environment is different when udev invokes it, > >> and my strace attempt with udev killed the system, so no info there. > >> > > > > Hmm, what about compiling with debug and getting a core then? > > Sure. debug is easy, -g, but you'll have to tell me how to get it > do produce a core dump. > See if adjusting /etc/security/limits.conf will enable it to dump core. Otherwise you'll have to stick 'ulimit -c unlimited' somewhere... -- Dmitry