From: Daniel Jacobowitz <drow@false.org>
To: Jiju George T <jiju.george@nestgroup.net>
Cc: gdb@sourceware.org
Subject: Re: Problem in using gdb 6.8 to step code in flash
Date: Wed, 14 May 2008 13:08:00 -0000 [thread overview]
Message-ID: <20080514130816.GA11707@caradoc.them.org> (raw)
In-Reply-To: <00b501c8b5c0$d47ed7d0$390aa8c0@ashmicro.ashling.com>
On Wed, May 14, 2008 at 01:48:38PM +0100, Jiju George T wrote:
> Â Â I checked the difference between these two and fond out that the issue is
> caused by the difference in the way sde-gdb and gdb 6.8 does step operation.
> SDE GDB issues step(s) command to GDB server where as gdb 6.8 tries to set
> breakpoint on next line and issue continue(c) command. Any idea on why the
> two gdb variants behave differently for step operation using same GDB
> server? How gdb decides what mechanism to be used for stepping operation?
Is your GDB configured for mips-linux? The SDE debugger is
configured for mips-elf. Try that configuration instead.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-05-14 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 12:49 Jiju George T
2008-05-14 13:08 ` Daniel Jacobowitz [this message]
2008-05-14 14:29 ` Jiju George T
2008-05-14 14:49 ` 'Daniel Jacobowitz'
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=20080514130816.GA11707@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=jiju.george@nestgroup.net \
/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