From: Lucien Anti-Spam <lucienmp_antispam@yahoo.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] m68k gdb has stopped single stepping correctly
Date: Wed, 23 Jan 2019 15:58:27 +0000 (UTC) [thread overview]
Message-ID: <251451940.431966.1548259107629@mail.yahoo.com> (raw)
In-Reply-To: 251451940.431966.1548259107629.ref@mail.yahoo.com
Hi folks,
I noticed that with 3.x release that the GDB options (-S -s) for certain CPU results in very weird stepping.Usually stops afer a few steps, whilst the stub continues responding the PC doesnt update, however, I have only deeply looked at the m68k.
In the case of the m68K the SR gets the trace bit set (T=10b), and the PC doesnt update.The m68k gdbstub, and main gdbstub seem mostly unchanged.But it seems the INSN handling has changed greatly for the m68k.
Does anyone have any ideas what happened?
Cheers,Luc
next parent reply other threads:[~2019-01-23 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <251451940.431966.1548259107629.ref@mail.yahoo.com>
2019-01-23 15:58 ` Lucien Anti-Spam [this message]
2019-01-23 18:08 ` [Qemu-devel] m68k gdb has stopped single stepping correctly Emilio G. Cota
2019-01-24 12:59 ` Lucien Anti-Spam
2019-01-24 13:38 ` Laurent Vivier
2019-01-24 13:38 ` Alex Bennée
2019-02-20 15:38 ` Thomas Huth
2019-02-21 7:39 ` Lucien Anti-Spam
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=251451940.431966.1548259107629@mail.yahoo.com \
--to=lucienmp_antispam@yahoo.com \
--cc=qemu-devel@nongnu.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).