public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: Tom Rini <trini@kernel.crashing.org>, Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Split kgdb into "lite" and "normal" parts
Date: Wed, 25 Feb 2004 12:49:28 +0530	[thread overview]
Message-ID: <200402251249.28519.amitkale@emsyssoft.com> (raw)
In-Reply-To: <20040224233809.GK1052@smtp.west.cox.net>

On Wednesday 25 Feb 2004 5:08 am, Tom Rini wrote:
> On Wed, Feb 25, 2004 at 12:27:03AM +0100, Pavel Machek wrote:
> > Hi!
> >
> > > > > > Tested (core-lite.patch + i386-lite.patch + 8250.patch)
> > > > > > combination. Looks good.
> > > > > >
> > > > > > Let's first check this in and then do more cleanups.
> > > > > > Tom, does it sound ok?
> > > > >
> > > > > This sounds fine to me.  Pavel, I'm guessing you did this with
> > > > > quilt, could you provide some pointers on how to replicate this in
> > > > > the future?
> > > >
> > > > Unfortunately, I done it by hand :-(. But if -lite parts are not
> > > > merged, soon, I'll be forced to start using quilt. Doing stuff by
> > > > hand is quite painfull...
> > >
> > > There's still a whole bunch of bogons in the -lite patch still, so I
> > > don't think it should be merged yet.
> >
> > Well, it seems to contains a *lot* less bogons than what currently is
> > in -mm series.
> >
> > What big problems do you see? It does not yet use weak symbols, but I
> > do not think that's a serious problem. What else?
>
> The first two big ones are:
> - Doesn't like gdb 6.0 (You cannot assume the first packet is Hc...)

Can you tell me more about this?

> - Wierdities with kgdb_killed_or_detached / kgdb_might_be_resumed
>   (both can die).

Yes. These have to be thought over again. I don't think a perfect solution 
exists for all problems related to gdb kill/die followed by a reattach. We 
should attempt a proper design describing different scenarios.

> - All of the function pointer games (of which the weak symbols, but not
>   all of them) are a part of.
> - Issues w/ handling 'D' and 'k' packets cleaner (and I think there was
>   a correctness fix in there, too, but it was a while ago).

Is this wrt kgdb_killed.., kgdb_might..., remove breakpoints?

> - Don't ACK packets sitting on the line

More info please.

-Amit

> - kgdb_schedule/process_breakpoint, required for kgdboe, harmless to use
>   on serial.
>
> There's still a lot of stuff I checked into linux-2.6-kgdb that's
> non-trivially important
> (http://ppc.bkbits.net:8080/linux-2.6-kgdb/ChangeSet@-4w?nav=index.html)


  parent reply	other threads:[~2004-02-25  7:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 22:50 Split kgdb into "lite" and "normal" parts Pavel Machek
2004-02-19  7:52 ` Amit S. Kale
2004-02-24 21:39   ` Tom Rini
2004-02-24 22:15     ` Pavel Machek
2004-02-24 23:21       ` Tom Rini
2004-02-24 23:27         ` Pavel Machek
2004-02-24 23:38           ` Tom Rini
2004-02-24 23:49             ` Pavel Machek
2004-02-24 23:57               ` Tom Rini
2004-02-25  0:08                 ` Pavel Machek
2004-02-25  7:15                   ` Amit S. Kale
2004-02-25  7:19             ` Amit S. Kale [this message]
2004-02-25 15:58               ` Tom Rini
2004-02-25 20:58                 ` 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=200402251249.28519.amitkale@emsyssoft.com \
    --to=amitkale@emsyssoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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