From: Tom Rini <trini@kernel.crashing.org>
To: "Amit S. Kale" <amitkale@emsyssoft.com>
Cc: Pavel Machek <pavel@suse.cz>, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Split kgdb into "lite" and "normal" parts
Date: Wed, 25 Feb 2004 13:58:11 -0700 [thread overview]
Message-ID: <20040225205811.GC1052@smtp.west.cox.net> (raw)
In-Reply-To: <20040225155823.GP1052@smtp.west.cox.net>
On Wed, Feb 25, 2004 at 08:58:23AM -0700, Tom Rini wrote:
> On Wed, Feb 25, 2004 at 12:49:28PM +0530, Amit S. Kale wrote:
> > On Wednesday 25 Feb 2004 5:08 am, Tom Rini wrote:
[snip]
> > > - 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?
>
> This will be part of the patch I hope to post today:
> http://ppc.bkbits.net:8080/linux-2.6-kgdb/patch@1.1500.2.19?nav=index.html|ChangeSet@-4w|cset@1.1500.2.19
After looking at what's in your stub now, and at the gdb source code,
I've filed a gdb bug (remote/1571) as the protocol docs and code don't
agree on what's expected from a detach. The docs say that gdb doesn't
look for a reply (so we wouldn't/shouldn't make one) but the code does,
and will print out an error code, if one happens. So I'm going to leave
this bit of code alone for now.
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2004-02-25 21:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 22:50 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
2004-02-25 15:58 ` Tom Rini
2004-02-25 20:58 ` Tom Rini [this message]
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=20040225205811.GC1052@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=amitkale@emsyssoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®