From: Matt Porter <mporter@kernel.crashing.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PPC debug setcontext syscall implementation
Date: Thu, 2 Dec 2004 15:49:02 -0700 [thread overview]
Message-ID: <20041202154901.B20211@home.com> (raw)
In-Reply-To: <20041202222349.GE14005@smtp.west.cox.net>; from trini@kernel.crashing.org on Thu, Dec 02, 2004 at 03:23:50PM -0700
On Thu, Dec 02, 2004 at 03:23:50PM -0700, Tom Rini wrote:
> On Thu, Dec 02, 2004 at 02:41:32PM -0600, Corey Minyard wrote:
>
> > Hello all,
> >
> > I have attached a patch with the implementation of the debug_setcontext
> > system call. The syscall has been reserved for a while and I've posted
> > this before. So I've ported to the newest kernel and here it is again.
> >
> > This syscall allows signal handlers to perform debug functions. It
> > allows the signal handler to turn on single-stepping, for instance, and
> > the thread will get a trap after executing the next instruction. It can
> > also (on supported PPC processors) turn on branch tracing and get a trap
> > after the next branch instruction is executed. This is useful for
> > in-application debugging.
>
> I asked Corey off-list, and this is vs 2.6.10-rc2-mm3.
> I propose (and will update the patch tracker
> (http://ozlabs.org/ppc32-patches/, I don't recall if/how well it was
> advertised)) that so long as KGDB still works (I'll even go test it on
> classic) as well as GDB testsuite (this is a 'touchy' area, so I'd like
> to well-test changes) is still 'OK', pushing this into 2.6.11.
I don't see a problem so long as both the 40x||booke and classic paths
are tested with gdb and kgdb. I don't want to fix the former path again.
-Matt
next prev parent reply other threads:[~2004-12-02 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 20:41 PPC debug setcontext syscall implementation Corey Minyard
2004-12-02 22:23 ` Tom Rini
2004-12-02 22:49 ` Matt Porter [this message]
2004-12-02 22:58 ` Corey Minyard
2004-12-02 23:16 ` Tom Rini
2004-12-03 22:07 ` Corey Minyard
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=20041202154901.B20211@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).