linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: pt_regs.dbcr0/1
Date: Tue, 04 Jun 2002 13:22:13 -0400	[thread overview]
Message-ID: <3CFCF745.8090002@embeddededge.com> (raw)
In-Reply-To: 15612.18916.648386.173632@argo.ozlabs.ibm.com


Paul Mackerras wrote:

> So has anyone done a 4xx-aware gdb yet?

Not to my knowledge.  Daniel Jacobowitz (drow) has discussed it a little,
but I have not heard much about it lately.

> ....  I think we are in violent agreement. :)

Not again......It must be that Aussie English :-)


> ..... gdb + xmon/kgdb
> may be possible but we will have to see how complex it looks once we
> know what the kernel support for gdb looks like.

I believe we have tied the BDI context switch configuration option to
allowing external debugging by ensuring the kernel doesn't mess around
with the debug registers.  We have at least discussed doing it.  As
long as we properly context switch the debug registers, all of the software
modes should coexist happily.

Thanks.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-04 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01  5:08 pt_regs.dbcr0/1 Paul Mackerras
2002-06-03  6:04 ` pt_regs.dbcr0/1 Armin
2002-06-04  1:23 ` pt_regs.dbcr0/1 Dan Malek
2002-06-04  5:02   ` pt_regs.dbcr0/1 Paul Mackerras
2002-06-04 17:22     ` Dan Malek [this message]
2002-06-04 21:34       ` pt_regs.dbcr0/1 Kumar Gala
2002-06-04 22:00         ` pt_regs.dbcr0/1 Frank Rowand
2002-06-04 22:10         ` pt_regs.dbcr0/1 Dan Malek
2002-06-04 21:55 ` pt_regs.dbcr0/1 Frank Rowand
2002-06-04 22:03   ` pt_regs.dbcr0/1 Paul Mackerras

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=3CFCF745.8090002@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@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).