linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: sjk <jack.sun@bmrtech.com>
To: bgat@billgatliff.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: gdbserver and gdb cross debug?
Date: Mon, 18 Nov 2002 09:43:51 +0800	[thread overview]
Message-ID: <3DD845D7.5C98736B@bmrtech.com> (raw)
In-Reply-To: 20021115134822.A5906@saturn.billgatliff.com


"William A. Gatliff" wrote:

> Jikun:
>
> On Mon, Nov 11, 2002 at 03:39:07PM +0800, sjk 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.
>
> Have you compiled the application in question with optimizations?  Gdb
> isn't so good at debugging optimized code.  Compile with -g -O0 if you
> intend to debug.

I tried to compile hello.c as following:

ppc_405-gcc -g -O0 -o hello hello.c

Then set up the connection of gdbserver and ppc_405-gdb. The program could not
be debugged step by step either.
Is it possible that there is bug in ptrace.c or traps.c


Thanks a lot

Jikun

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

  reply	other threads:[~2002-11-18  1:43 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
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 [this message]
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=3DD845D7.5C98736B@bmrtech.com \
    --to=jack.sun@bmrtech.com \
    --cc=bgat@billgatliff.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).