public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: George Anzinger <george@mvista.com>
Cc: "Amit S. Kale" <amitkale@emsyssoft.com>,
	Hollis Blanchard <hollisb@us.ibm.com>,
	KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Powerpc Linux <linuxppc-dev@lists.linuxppc.org>
Subject: Re: PPC KGDB changes and some help?
Date: Thu, 22 Jan 2004 15:52:09 -0700	[thread overview]
Message-ID: <20040122225209.GS15271@stop.crashing.org> (raw)
In-Reply-To: <401052D1.4040306@mvista.com>

On Thu, Jan 22, 2004 at 02:46:41PM -0800, George Anzinger wrote:
> Tom Rini wrote:
> >
> >
> >FWIW, this is true of KGDB on all PPCs.  IIRC, so long as the serial
> >definitions are filled out statically, the stub currently in kernel.org
> >for PPC can do first-line-of-C already.
> >
> >
> >>How about changing the code in kgdbstub to allow kgdb to be configured in 
> >>one of the following ways:
> >>Late kgdb - kgdb comes up after smp_init in the kernel boot sequence. 
> >>kgdb8250 can be used with more flexibility through kernel command line 
> >>options. One can boot a kgdb kernel without activating kgdb. Works with 
> >>the interface chosen by kernel command line (kgdb8250 and kgdbeth for the 
> >>moment).
>
> A further thought on this.  I think kgdb should take control on oops, panic 
> and other bad news things.  This without being anthing but configured in.  
> Thus the command line options to set up the interface, etc, should not 
> automatically connect to gdb.

*confused look* it doesn't do this already on i386?  I'm fairly certain
that it does on PPC, regardless of the stub (since I've got this wierd
panic happening on my testbox right now, but kgdb is kicking in..)

-- 
Tom Rini
http://gate.crashing.org/~trini/

  reply	other threads:[~2004-01-22 22:52 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040120172708.GN13454@stop.crashing.org>
     [not found] ` <200401211946.17969.amitkale@emsyssoft.com>
     [not found]   ` <20040121153019.GR13454@stop.crashing.org>
2004-01-21 16:53     ` PPC KGDB changes and some help? Amit S. Kale
2004-01-21 18:42       ` Tom Rini
2004-01-21 19:21         ` Tom Rini
2004-01-21 19:22           ` Tom Rini
2004-01-22 17:44             ` Tom Rini
2004-01-22 18:05               ` Tom Rini
2004-01-23 22:46                 ` Tom Rini
2004-01-23 23:38                   ` George Anzinger
2004-01-26 20:46                     ` Tom Rini
2004-01-26 21:27                       ` George Anzinger
2004-01-26 21:42                         ` Tom Rini
2004-01-26 22:35                           ` George Anzinger
2004-01-26 21:45                       ` George Anzinger
2004-01-26 22:06                         ` Tom Rini
2004-01-27  9:05                           ` Amit S. Kale
2004-01-24  0:48                   ` George Anzinger
2004-01-24  3:47                   ` [PATCH] Kgdb dwarf2 for asm George Anzinger
2004-01-27 18:22                   ` PPC KGDB changes and some help? Tom Rini
2004-01-21 22:03           ` Tom Rini
2004-01-21 23:12           ` George Anzinger
2004-01-22 15:07             ` Tom Rini
2004-01-22 15:25               ` Hollis Blanchard
2004-01-22 15:45                 ` Tom Rini
2004-01-22 16:06                   ` Amit S. Kale
2004-01-22 16:45                     ` Tom Rini
2004-01-22 22:46                       ` George Anzinger
2004-01-22 22:52                         ` Tom Rini [this message]
2004-01-22 23:09                           ` George Anzinger
2004-01-22 22:35                     ` George Anzinger
2004-01-23 17:08                     ` Tom Rini
2004-01-22 21:54                   ` George Anzinger
2004-01-26 21:32           ` Tom Rini
2004-01-27  8:59             ` Amit S. Kale
2004-01-21 23:05         ` George Anzinger
2004-01-22 15:03           ` 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=20040122225209.GS15271@stop.crashing.org \
    --to=trini@kernel.crashing.org \
    --cc=amitkale@emsyssoft.com \
    --cc=george@mvista.com \
    --cc=hollisb@us.ibm.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.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