Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262257AbVAQQjC (ORCPT ); Mon, 17 Jan 2005 11:39:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262258AbVAQQjB (ORCPT ); Mon, 17 Jan 2005 11:39:01 -0500 Received: from fw.osdl.org ([65.172.181.6]:5047 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S262257AbVAQQi5 (ORCPT ); Mon, 17 Jan 2005 11:38:57 -0500 Date: Mon, 17 Jan 2005 08:38:25 -0800 (PST) From: Linus Torvalds To: Tigran Aivazian cc: "H. Peter Anvin" , Jan Hubicka , Jack F Vogel , linux-kernel@vger.kernel.org Subject: Re: [discuss] booting a kernel compiled with -mregparm=0 In-Reply-To: Message-ID: References: <20050114205651.GE17263@kam.mff.cuni.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1021 Lines: 24 On Mon, 17 Jan 2005, Tigran Aivazian wrote: > > So, this means there is no way for kdb on x86_64 to show the parameter > values for each function in the back trace. Any chance of changing the > ABI/x86_64 to do the right (i.e. passing via stack like on i386) thing > now? Then kdb would automatically support it via normal ar-handling code. "right thing"? You have a very strange definition of "right". The x86 is pretty much the only architecture still in use that passes everything on the stack by default, and even there it's considered pretty painful (and is not true of FP arguments). If a debugger cannot handle arguments in registers, it by definition cannot handle things like alpha/ppc/mips/xxx, so I'd say that the debugger is seriously broken. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/