public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: lkundrak@v3.sk
To: gdb-gnats@sources.redhat.com
Subject: remote/2454: GDB sets register 29 on i386 upon stop for no known reason
Date: Tue, 06 May 2008 07:48:00 -0000 [thread overview]
Message-ID: <20080506074652.27524.qmail@sourceware.org> (raw)
>Number: 2454
>Category: remote
>Synopsis: GDB sets register 29 on i386 upon stop for no known reason
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue May 06 07:48:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: lkundrak@v3.sk
>Release: gdb-6.8
>Organization:
>Environment:
Linux localhost.localdomain 2.6.25-8.fc9.i686 #1 SMP Wed Apr 23 03:56:19 EDT 2008 i686 athlon i386 GNU/Linux
This GDB was configured as "i386-redhat-linux-gnu".
Reproduced with 6.8 with lot of Red Hat patches in Fedora
Also happens to branch of gdb-6.7.50 with python support, without any additional patches
>Description:
This happens upon stop on a breakpoint:
Packet received: T054:e47d0600;5:f87d0600;8:39610900;
Sending packet: $g#67...Ack
Packet received: 405303000000000000000000a05f0900e47d0600f87d060000000000405303003961090006000000080000001000000010000000100000001000000010000000
Sending packet: $P8=38610900#60...Ack
Packet received: OK
Packet P (set-register) is supported
Sending packet: $P29=ffffffff#28...Ack
Packet received: E01
Remote failure reply: E01
(gdb)
My GDB stub returns E01 because register that is attempted to be set -- 29 -- is more than is known about; 16. "info registers" also outputs just 16 registers.
If I ignore the command, and send "OK" instead of "E01", it seems to have no impact at all.
I am wonering whether problem may lay in my remote GDB stub (that is based on one shipped with GDB) or if that's GDB's problem and if backtrace from GDB from function that sends the P command might be helpful?
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2008-05-06 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 7:48 lkundrak [this message]
2008-05-06 12:38 Daniel Jacobowitz
2008-05-06 14:45 drow
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=20080506074652.27524.qmail@sourceware.org \
--to=lkundrak@v3.sk \
--cc=gdb-gnats@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).