From: Dan Malek <dan@mvista.com>
To: Ed.Swarthout@motorola.com
Cc: paulus@samba.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: interesting line in process.c
Date: Mon, 15 Oct 2001 11:54:15 -0400 [thread overview]
Message-ID: <3BCB06A7.7A6C0D9F@mvista.com> (raw)
In-Reply-To: 200110151547.f9FFltD24916@pacific.somerset.sps.mot.com
Edward Swarthout wrote:
> I would suggest ppc do the same thing and define a single debug array
> in thread_struct which contains the processor specific debug registers
> needed to support gdb's use of hardware breakpoints.
So, gdb has knowledge of hardware breakpoints and knows how to use
them across the different processors? I would ask we consider using
a standard breakpoint interface to the kernel and allow the kernel
to implement the breakpoints as it desires. It seems having this
knowledge and synchronizing the necessary information across the
interface could be challenging.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-10-15 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-13 11:56 interesting line in process.c Paul Mackerras
2001-10-13 17:14 ` Daniel Jacobowitz
2001-10-15 14:38 ` Dan Malek
2001-10-15 15:47 ` Edward Swarthout
2001-10-15 15:54 ` Dan Malek [this message]
2001-10-15 17:44 ` Daniel Jacobowitz
2001-10-20 1:42 ` Dan Malek
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=3BCB06A7.7A6C0D9F@mvista.com \
--to=dan@mvista.com \
--cc=Ed.Swarthout@motorola.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).