Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Stan Sieler <sieler@allegro.com>
To: frowand@mvista.com
Cc: law@redhat.com, dave@hiauly1.hia.nrc.ca (John David Anglin),
	rhirst@linuxcare.com (Richard Hirst),
	parisc-linux@puffin.external.hp.com
Subject: Re: [parisc-linux] Single-stepping
Date: Wed, 15 Nov 2000 13:47:15 -0800 (PST)	[thread overview]
Message-ID: <200011152147.NAA23824@opus.allegro.com> (raw)
In-Reply-To: <3A12FD2C.665AEF89@mvista.com> from "Frank Rowand" at Nov 15, 2000 01:16:28 PM

Re:

> I implemented two different single step algorithms for a a _kernel_ debugger
> for hp-ux.  The algorithm used could be chosen by a compile switch, because

BTW, Frank, ask Lee Courtney at MontaVista about Debug/iX ...
we've had kernel debugging and single stepping (except for the interrupt 
control stack and a few other corner cases) for 15+ years.

It's *very* powerful to be able to logon as root (or equivalent) and set
breakpoints within the kernel, hit them, and then single step 
... all on a standard release of the operating system.

> I liked the recovery counter method better than my second method (but had to
> deal with collisions with the other kernel services).  My second method was
> to insert a breakpoint at the target of the single step.  It's a pain to do
> that because of issues with delay slots, branching, and nullification.

Worse yet...the breakpoint mechanism raises hell if you have more than
one CPU :)    You realllly don't want that other CPU to hit the breakpoint!
 
-- 
Stan Sieler                                           sieler@allegro.com
www.allegro.com/sieler/wanted/index.html                  www.sieler.com        

  reply	other threads:[~2000-11-15 21:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15 18:48 [parisc-linux] Single-stepping Richard Hirst
2000-11-15 19:49 ` John David Anglin
2000-11-15 20:30   ` law
2000-11-15 21:16     ` Frank Rowand
2000-11-15 21:47       ` Stan Sieler [this message]
2000-11-15 21:08   ` Stan Sieler
2000-11-16 12:09   ` Richard Hirst

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=200011152147.NAA23824@opus.allegro.com \
    --to=sieler@allegro.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=frowand@mvista.com \
    --cc=law@redhat.com \
    --cc=parisc-linux@puffin.external.hp.com \
    --cc=rhirst@linuxcare.com \
    /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