From: Juha Aaltonen <turbopultti@gmail.com>
To: gdb@sourceware.org
Subject: Known bug in remote serial protocol, or something else?
Date: Mon, 05 Oct 2015 12:39:00 -0000 [thread overview]
Message-ID: <CAHR0xd518aBQ1WXTZowazT=OuL_4F=6ywND7MDSra-=JqgaVpQ@mail.gmail.com> (raw)
I was trying to debug my "standalone gdbstub" when I encountered a
strange problem.
I loaded a debuggee program and started executing it, and it crashed
in a weird address.
When I disassembled the code (ARMv7 target) I found out that some
instructions were corrupted.
I couldn't figure it out about binary transfer (Looked like UTF-8, but
didn't quite match), so I disabled
the 'X'-command, and the 'M'-command seemed to do even worse - telling
by the debug messages
(set debug serial 1, set debug remote 1).
The gdb client I'm using is gdb-multiarch 7.7.1 on Debian 8 (x86_64) -
the one in the official repo.
I'm happy to supply further info, if it could be of any help -
including the debuggee ELF, but maybe this
mailing list is not the place...
next reply other threads:[~2015-10-05 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 12:39 Juha Aaltonen [this message]
2015-10-05 14:51 ` Paul_Koning
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='CAHR0xd518aBQ1WXTZowazT=OuL_4F=6ywND7MDSra-=JqgaVpQ@mail.gmail.com' \
--to=turbopultti@gmail.com \
--cc=gdb@sourceware.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