From: Duane Voth <duanev@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1703147] [NEW] Xfer:features:read truncating xml sent to gdb frontends
Date: Sat, 08 Jul 2017 21:19:03 -0000 [thread overview]
Message-ID: <149954874338.15421.5827897782818416258.malonedeb@wampee.canonical.com> (raw)
Public bug reported:
Around line 1326 in gdbstub.c:
if (len > (MAX_PACKET_LENGTH - 5) / 2)
len = (MAX_PACKET_LENGTH - 5) / 2;
is truncating processor reg description xml files longer than 2045
bytes. Deleting these lines works for my immediate need, but they seem
to be trying to fix some buffer overrun condition so I won't offer a
patch until we understand their purpose.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1703147
Title:
Xfer:features:read truncating xml sent to gdb frontends
Status in QEMU:
New
Bug description:
Around line 1326 in gdbstub.c:
if (len > (MAX_PACKET_LENGTH - 5) / 2)
len = (MAX_PACKET_LENGTH - 5) / 2;
is truncating processor reg description xml files longer than 2045
bytes. Deleting these lines works for my immediate need, but they
seem to be trying to fix some buffer overrun condition so I won't
offer a patch until we understand their purpose.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1703147/+subscriptions
next reply other threads:[~2017-07-08 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-08 21:19 Duane Voth [this message]
2017-07-08 21:44 ` [Qemu-devel] [Bug 1703147] [NEW] Xfer:features:read truncating xml sent to gdb frontends Peter Maydell
2021-05-02 5:41 ` [Bug 1703147] " Thomas Huth
2021-07-02 4:17 ` Launchpad Bug Tracker
2021-07-02 4:48 ` Duane Voth
2021-07-02 6:49 ` Thomas Huth
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=149954874338.15421.5827897782818416258.malonedeb@wampee.canonical.com \
--to=duanev@gmail.com \
--cc=1703147@bugs.launchpad.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.