From: "Andreas Färber" <afaerber@suse.de>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] gdb: Fix gdb error
Date: Mon, 12 Aug 2013 19:40:09 +0200 [thread overview]
Message-ID: <52091DF9.1080703@suse.de> (raw)
In-Reply-To: <87bo53b73y.fsf@linux.vnet.ibm.com>
Am 12.08.2013 11:17, schrieb Aneesh Kumar K.V:
> Andreas Färber <afaerber@suse.de> writes:
>> Am 11.08.2013 20:14, schrieb Aneesh Kumar K.V:
>>> From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
>>>
>>> Don't update the global register count if not requested.
>>> Without this patch a remote gdb session gives
>>>
>>> (gdb) target remote localhost:1234
>>> Remote debugging using localhost:1234
>>> Remote 'g' packet reply is too long:
>>> 0000000028000084c000000000ccba50c000000000c ...
>>> ....
>>> ...
>>> (gdb)
>>>
>>> This is a regression introduce by a0e372f0c49ac01faeaeb73a6e8f50e8ac615f34
>>>
>>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>>
>> Thanks for tracking this down. I'm willing to include a variation in
>> today's pull to fix 1.6.0-rc3. However, did you find an explanation
>> *why* it needs to be like this?
>
> IIUC our reply packet for 'g' contain more data becaue we ended up with
> larger cpu->gdb_num_regs. This only happens for archs that do a
> gdb_register_coprocessor with gpos == 0. The older code didn't update
> num_g_regs in that case. Not sure why we do like that
>
>> I understand it is a revert to using the
>> static variable, updated to using the CPUClass field rather than the
>> previous preprocessor constant.
>>
>
> I don't really like the patch. But I also don't know enough to fix this
> without using the static variable. If you want me to try another
> version please send it across. I can easily reproduce this on PowerPC.
While it's always unfortunate to have a known breakage, we decided it's
too late/risky to address this for -rc3 today.
I put together a different patch that hopefully fixes the breakage while
avoiding to revert to static variables:
http://patchwork.ozlabs.org/patch/266594/
If this fixes things for you and doesn't break other things, we can get
it into qemu.git after Thursday [1] and backport it into 1.6.1.
Regards,
Andreas
[1] http://wiki.qemu.org/Planning/1.6
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-08-12 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 18:14 [Qemu-devel] [PATCH] gdb: Fix gdb error Aneesh Kumar K.V
2013-08-12 8:48 ` Andreas Färber
2013-08-12 9:17 ` Aneesh Kumar K.V
2013-08-12 17:40 ` Andreas Färber [this message]
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=52091DF9.1080703@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.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).