All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Prosun Niyogi <pniyogi@us.ibm.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: KGDB on BookE
Date: Mon, 13 Jun 2005 09:40:14 -0700	[thread overview]
Message-ID: <42ADB6EE.30205@am.sony.com> (raw)
In-Reply-To: <OF6BE916AF.4D6A65C4-ON8625701F.004ACEBA-8625701F.004B9D77@us.ibm.com>

Prosun Niyogi wrote:
> 
> I've grabbed latest kernel.org kernel (2.6.11.11) to attempt to get a
> working kgdb on my ebony setup. Checking the mailing list archives, it
> seems as if all the 4xx specific kgdb patches have been merged with
> kernel.org. Is this the case? If so, I have a problem single stepping
> using kgdb. The debugger_sstep(regs) function is never called from
> traps.c. So, as of right now.. I can only set/hit an arbitrary
> breakpoint (for my testing, I've been setting a breakpoint at sys_sync).
> After setting the breakpoint and continuing from the initial kgdb entry
> point, gdb successfully catches the breakpoint at sys_sync, but when I
> attempt to step, the kernel continues normal operation, and subsequent
> attempts at breaking into gdb control by issuing a "sync" command on the
> ebony terminal in minicom do not hit the breakpoint. Any
> pointers/suggestions as to where I can obtain a working kgdb-enabled
> kernel for the ebony board? Any assistance would be helpful.
> 

Apply the patches in CVS from http://sourceforge.net/projects/kgdb

This works with 2.6.11.11 and Ebony with both serial and Ether connections, 
but I found the kernel hangs with CONFIG_PREEMPT=y.

-Geoff

      reply	other threads:[~2005-06-13 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 13:45 KGDB on BookE Prosun Niyogi
2005-06-13 16:40 ` Geoff Levand [this message]

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=42ADB6EE.30205@am.sony.com \
    --to=geoffrey.levand@am.sony.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=pniyogi@us.ibm.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 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.