linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: sjk <jack.sun@bmrtech.com>
To: "Dr. Craig Hollabaugh" <craig@hollabaugh.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: gdbserver and gdb cross debug?
Date: Mon, 11 Nov 2002 15:57:22 +0800	[thread overview]
Message-ID: <3DCF62E2.89F1C882@bmrtech.com> (raw)
In-Reply-To: 20021111074041.EBB0127DE1@chuy.ouraynet.com


Dr. Craig,

I am using MontaVista Linux LSP. The ibm-walnut-ppc405gp LSP works correctly
on walnut board. We can cross debug applications by ppc_405-gdb and
gdbserver(version 5.1).
But the following problem occurs on EP405 board.
Is it possible that the problem is caused by library, memory or initialization
of PPC405GP registers?

Sun

"Dr. Craig Hollabaugh" wrote:

> > I am porting Linux on EP405 board. So I use gdbserver and gdb to debug
> > applications,but only the first
> > breakpoint could be stopped.Then if i press 'step', the program will
> > execute to end straightforwardly . Any other breakpoints could not break
> > the execution.
>
> Which tools are you using? I've been using the fine ELDK from denx on a
> walnut board without problems like you mention above.

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

  reply	other threads:[~2002-11-11  7:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200210260458.g9Q4wpq15745@ftp1.mvista.com>
2002-11-04  8:51 ` Why the gdbserver can't debug step by step? sjk
2002-11-11  7:39 ` gdbserver and gdb cross debug? sjk
2002-11-11  7:40   ` Dr. Craig Hollabaugh
2002-11-11  7:57     ` sjk [this message]
2002-11-11 13:12   ` Kenneth Johansson
2002-11-11 13:55     ` Andreas Beranek
2002-11-11 14:18       ` Kenneth Johansson
2002-11-11 15:33     ` Wolfgang Denk
2002-11-15 19:48   ` William A. Gatliff
2002-11-18  1:43     ` sjk
2002-11-18  8:16       ` Kenneth Johansson

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=3DCF62E2.89F1C882@bmrtech.com \
    --to=jack.sun@bmrtech.com \
    --cc=craig@hollabaugh.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).