From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takashi Iwai <tiwai@suse.de>
Subject: Re: ALSA become "Segmentation fault" on current linus
	tree
Date: Tue, 05 Jul 2011 08:06:01 +0200
Message-ID: <s5hpqlpfeie.wl%tiwai@suse.de>
References: <87k4bxfjue.wl%kuninori.morimoto.gx@renesas.com>
	<s5hvcvhffnt.wl%tiwai@suse.de>
	<87ei25fewa.wl%kuninori.morimoto.gx@renesas.com>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15])
	by alsa0.perex.cz (Postfix) with ESMTP id C1403103889
	for <alsa-devel@alsa-project.org>;
	Tue,  5 Jul 2011 08:06:04 +0200 (CEST)
In-Reply-To: <87ei25fewa.wl%kuninori.morimoto.gx@renesas.com>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Sender: alsa-devel-bounces@alsa-project.org
Errors-To: alsa-devel-bounces@alsa-project.org
To: kuninori.morimoto.gx@renesas.com
Cc: Linux-ALSA <alsa-devel@alsa-project.org>, Mark Brown <broonie@opensource.wolfsonmicro.com>, Kuninori Morimoto <morimoto.kuninori@gmail.com>, Liam Girdwood <lrg@slimlogic.co.uk>
List-Id: alsa-devel@alsa-project.org

At Tue, 05 Jul 2011 14:57:41 +0900,
kuninori.morimoto.gx@renesas.com wrote:
> 
> 
> Dear Takashi
> 
> Thanks for your reply
> 
> > Hm, this should have been fixed by the later commit:
> >   commit 2b39535b9e54888649923beaab443af212b6c0fd
> >   Author: Jarkko Nikula <jhnikula@gmail.com>
> >   Date:   Fri May 20 15:47:40 2011 +0300
> > 
> >     ASoC: core: Don't set "(null)" as a driver name
> > 
> > Could you check whether the segfault occurs at this point?
> > It's possible that another bug was introduced after it, of course.
> 
> Hmm...
> segfault still happen on this commit.

Can you trap the segfault via gdb to see where it happens?


Takashi