All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gerhard Pircher" <gerhard_pircher@gmx.net>
To: linuxppc-dev@ozlabs.org
Subject: Hardware debuggers for PPC74xx G4 CPUs
Date: Tue, 13 Nov 2007 22:48:45 +0100	[thread overview]
Message-ID: <20071113214845.85820@gmx.net> (raw)

I'm trying to debug a kernel lockup that occurs on my machine with all kernel
versions >2.6.16. I don't have a clue what the root cause of this lockup is,
thus I'm thinking about using a hardware debugger. Can anybody recommend a
reasonably cheap hardware debugger that works with G4 CPUs and can interact
with GDB/DDD?

regards,

Gerhard
-- 
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

             reply	other threads:[~2007-11-13 21:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 21:48 Gerhard Pircher [this message]
2007-11-13 21:57 ` Hardware debuggers for PPC74xx G4 CPUs Grant Likely
2007-11-13 21:59   ` Grant Likely
2007-11-13 22:10     ` Jon Smirl
2007-11-13 22:21       ` Gerhard Pircher
2007-11-14  1:17         ` Benjamin Herrenschmidt
2007-11-14  9:20           ` Gerhard Pircher
2007-11-13 23:23     ` Dan Malek
2007-11-13 23:39       ` Olof Johansson
2007-11-13 23:53         ` Jon Smirl
2007-11-14  1:17           ` Benjamin Herrenschmidt
2007-11-14  1:32             ` Jon Smirl
2007-11-15  1:35               ` Jerry Van Baren
2007-11-15  2:34                 ` Jon Smirl
2007-11-18  0:47                   ` Wolfgang Denk
2007-11-22 23:37                     ` Benjamin Herrenschmidt
2007-11-23  0:00                       ` Jon Smirl
2007-11-23  0:22                         ` Benjamin Herrenschmidt
2007-11-23 15:03                           ` Jon Smirl
2007-11-23 20:26                             ` Jon Smirl
2007-11-23 20:30                               ` Grant Likely
2007-11-13 22:03   ` Jon Smirl

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=20071113214845.85820@gmx.net \
    --to=gerhard_pircher@gmx.net \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.