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
Date: Wed, 3 Mar 2004 21:44:10 -0800 [thread overview]
Message-ID: <20040303214410.1ba0ab9d.akpm@osdl.org> (raw)
In-Reply-To: <200403041059.43439.amitkale@emsyssoft.com>
"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.
next prev parent reply other threads:[~2004-03-04 5:44 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040204230133.GA8702@elf.ucw.cz.suse.lists.linux.kernel>
[not found] ` <20040204155452.4 9c1eba8.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20040204152137.500e8319.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <402182B8.7030900@timesys.com.suse.lists.linux.kernel>
[not found] ` <20040204155452.49c1eba8.akpm@osdl.org.suse.lists.linux.kernel>
2004-02-05 3:11 ` Andi Kleen
2004-02-05 12:16 ` Pavel Machek
2004-02-05 17:50 ` Amit S. Kale
2004-02-06 2:20 ` Andi Kleen
2004-02-06 11:58 ` Amit S. Kale
2004-02-06 12:16 ` Andi Kleen
2004-02-06 13:05 ` Amit S. Kale
2004-02-06 13:24 ` Andi Kleen
2004-02-06 13:44 ` Amit S. Kale
2004-02-28 0:05 ` George Anzinger
2004-03-01 9:38 ` Amit S. Kale
2004-03-02 21:10 ` George Anzinger
2004-03-02 21:27 ` Andrew Morton
2004-03-02 23:52 ` George Anzinger
2004-03-03 5:08 ` Amit S. Kale
2004-03-03 16:06 ` Tom Rini
2004-03-04 0:42 ` George Anzinger
2004-03-03 10:05 ` Andi Kleen
2004-03-04 0:43 ` George Anzinger
2004-03-04 0:50 ` Andi Kleen
2004-03-04 5:06 ` Amit S. Kale
2004-03-04 5:18 ` Andrew Morton
2004-03-04 5:29 ` Amit S. Kale
2004-03-04 5:44 ` Andrew Morton [this message]
2004-03-04 20:54 ` George Anzinger
2004-03-04 21:03 ` Tom Rini
2004-03-04 23:15 ` George Anzinger
2004-03-04 13:01 ` Andi Kleen
2004-02-11 14:52 ` Amit S. Kale
2004-02-10 21:56 ` George Anzinger
2004-02-13 19:42 ` Andi Kleen
2004-02-12 1:34 ` George Anzinger
2004-02-12 8:33 ` Andi Kleen
2004-02-27 21:09 ` Piet Delaney
2004-02-27 21:58 ` George Anzinger
2004-02-27 23:33 ` Pavel Machek
2004-02-04 23:01 Pavel Machek
2004-02-04 23:21 ` Andrew Morton
2004-02-04 23:24 ` Pavel Machek
2004-02-04 23:45 ` Andrew Morton
2004-02-04 23:55 ` Tom Rini
2004-02-05 0:16 ` Andrew Morton
2004-02-05 0:23 ` Tom Rini
2004-02-20 0:15 ` George Anzinger
2004-02-04 23:39 ` La Monte H.P. Yarroll
2004-02-04 23:54 ` Andrew Morton
2004-02-05 1:19 ` Pavel Machek
2004-02-20 0:24 ` George Anzinger
2004-02-05 0:39 ` Pavel Machek
2004-02-04 23:52 ` Tom Rini
2004-02-05 0:17 ` Paul Mundt
2004-02-05 0:32 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040303214410.1ba0ab9d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=amitkale@emsyssoft.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=piggy@timesys.com \
--cc=trini@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome