From: Daniel Jacobowitz <drow@false.org>
To: Torsten Mohr <tmohr@s.netic.de>
Cc: gdb@sourceware.org, Keith Seitz <keiths@redhat.com>
Subject: Re: V850E simulator, assembler single-step never returns?!?
Date: Thu, 08 Jun 2006 01:22:00 -0000 [thread overview]
Message-ID: <20060607232402.GA26181@nevyn.them.org> (raw)
In-Reply-To: <200606080053.58952.tmohr@s.netic.de>
On Thu, Jun 08, 2006 at 12:53:58AM +0200, Torsten Mohr wrote:
> Is there some special support for debugging gdb?
No. You need to run it inside another debugger session using a native
GDB.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-07 23:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 19:42 Torsten Mohr
2006-06-05 20:42 ` Daniel Jacobowitz
2006-06-05 20:44 ` Keith Seitz
2006-06-05 20:50 ` Daniel Jacobowitz
2006-06-05 21:02 ` Keith Seitz
2006-06-05 22:36 ` Torsten Mohr
2006-06-05 22:41 ` Daniel Jacobowitz
2006-06-06 9:46 ` Torsten Mohr
2006-06-07 23:24 ` Torsten Mohr
2006-06-08 1:22 ` Daniel Jacobowitz [this message]
2006-06-08 12:12 ` Torsten Mohr
2006-06-08 21:37 ` Torsten Mohr
2006-06-05 20:34 Torsten Mohr
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=20060607232402.GA26181@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=keiths@redhat.com \
--cc=tmohr@s.netic.de \
/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