From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11707 invoked by alias); 9 Mar 2004 20:21:26 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 11699 invoked from network); 9 Mar 2004 20:21:26 -0000 Received: from unknown (HELO localhost.redhat.com) (216.129.200.20) by sources.redhat.com with SMTP; 9 Mar 2004 20:21:26 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 4DDF82B92; Tue, 9 Mar 2004 15:21:25 -0500 (EST) Message-ID: <404E2745.2090405@gnu.org> Date: Fri, 19 Mar 2004 00:09:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: jim.houston@comcast.net Cc: gdb-patches@sources.redhat.com Subject: Re: [patch] allow switching stacks References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03/txt/msg00211.txt.bz2 Message-ID: <20040319000900.MGqq4K-DigABQ3Rw1YUiCVpQtWjsAo0aYjcFLZgRwbw@z> > Hi Everyone, > > This patch against gdb-6.0 adds an option to disable an error check > which reports a non-contiguous stack as corrupted. I need this > option to get a reliable stack trace using kgdb on the x86-64 Linux > kernel because it uses a separate per-processor interrupt stack. > > This option is enabled with: > > set backtrace switch-stacks on > > Jim Houston - Concurrent Computer Corp. Can you provide more details of the problem -- exactly what do things look like at the stack switch? Your problem sounds very similar to the combination of a signal altstack and a signal trampoline - for such a situtation the stack direction check isn't applicable (pointing to the real bug). Andrew