From: Grant Grundler <grundler@parisc-linux.org>
To: Lev Assinovsky <LAssinovsky@algorithm.aelita.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Help: Need instruction sequence for gdb breakpoint
Date: Tue, 19 Aug 2003 22:37:02 -0600 [thread overview]
Message-ID: <20030820043702.GC24884@dsl2.external.hp.com> (raw)
In-Reply-To: <3F6F4712B759A34ABD453A8B39C10D62D4DA83@bagman.edm.com>
On Tue, Aug 19, 2003 at 02:47:47PM +0400, Lev Assinovsky wrote:
> Ok! But what's BREAK instruction for?
To force a trap into the kernel. That's not the same
as HW support since using break requires modifying the code stream
(remembering which instruction belonged there), flushing data-cache,
flush ins-cache, an dtrying to continue. The break's are fully
under SW control.
> Besides gdb works for me on HPUX 11.00
That's because HP has (had?) a team of folks working on the
"open source toolkit". parisc-linux hasn't been so lucky.
Alan Modra, Richard Hirst, Randolph Chung and a few others get gdb
working from time to time. But there is no dedicated maintainer
and that's what is needed.
grant
next prev parent reply other threads:[~2003-08-20 4:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 10:47 [parisc-linux] Help: Need instruction sequence for gdb breakpoint Lev Assinovsky
2003-08-20 4:37 ` Grant Grundler [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-25 12:16 Joel Soete
2003-08-25 8:31 Lev Assinovsky
[not found] <3F6F4712B759A34ABD453A8B39C10D62DEEC97@bagman.edm.com>
2003-08-23 6:21 ` Grant Grundler
2003-08-23 9:55 ` Thibaut VARENE
2003-08-19 10:37 Lev Assinovsky
2003-08-04 10:37 Lev Assinovsky
2003-08-19 10:28 ` Thibaut VARENE
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=20030820043702.GC24884@dsl2.external.hp.com \
--to=grundler@parisc-linux.org \
--cc=LAssinovsky@algorithm.aelita.com \
--cc=parisc-linux@lists.parisc-linux.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