Date: Wed, 3 Mar 2004 21:44:10 -0800
From: Andrew Morton <akpm@osdl.org>
To: "Amit S. Kale" <amitkale@emsyssoft.com>
Cc: ak@suse.de, george@mvista.com, pavel@ucw.cz, linux-kernel@vger.kernel.org,
       piggy@timesys.com, trini@kernel.crashing.org
Subject: Re: kgdb support in vanilla 2.6.2
Message-Id: <20040303214410.1ba0ab9d.akpm@osdl.org>
In-Reply-To: <200403041059.43439.amitkale@emsyssoft.com>
References: <20040204230133.GA8702@elf.ucw.cz.suse.lists.linux.kernel>
	<200403041036.58827.amitkale@emsyssoft.com>
	<20040303211850.05d44b4a.akpm@osdl.org>
	<200403041059.43439.amitkale@emsyssoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 782
Lines: 19

"Amit S. Kale" <amitkale@emsyssoft.com> wrote:
>
> To a user it'll appear as a 
>  message printed from gdb "Page fault at 0x1234" followed by gdb showing a 
>  SIGSEGV etc.

Well that would be nice.  Bear in mind that one usage scenario is to say
"hey, machine 342 has stopped responding" and to then fire up gdb and
connect to that machine with kgdboe.

In other words: if we rely on a gdb instance being connected at the time of
the exception, that message will be lost.  There needs to be a way of
retrieving the message post-facto.

-
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/