Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964873AbVLNSbL (ORCPT ); Wed, 14 Dec 2005 13:31:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964861AbVLNSbL (ORCPT ); Wed, 14 Dec 2005 13:31:11 -0500 Received: from cantor2.suse.de ([195.135.220.15]:11216 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S964835AbVLNSbI (ORCPT ); Wed, 14 Dec 2005 13:31:08 -0500 To: Dave Cc: linux-kernel@vger.kernel.org Subject: Re: x86_64 segfault error codes References: <8746466a0512141017j141d61dft3dd2b1ab95dc2351@mail.gmail.com> From: Andi Kleen Date: 14 Dec 2005 19:31:07 +0100 In-Reply-To: <8746466a0512141017j141d61dft3dd2b1ab95dc2351@mail.gmail.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 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: 702 Lines: 12 Dave writes: > For segfault error codes on x86_64, bits 0-3 are documented in > arch/x86_64/mm/fault.c. However, I am getting error 0x14 and 0x15 with this > particular user app when it segfaults. Is bit 4 valid and what does that > imply? bit 4 is documented too in 2.6. It means it was an instruction fetch. The error code is just the architectural error code for page faults BTW, see the Intel and AMD manuals for details. -Andi - 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/