From: Luis Machado <lgustavo@codesourcery.com>
To: Orgad Shaneh <orgads@gmail.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: PR13984 - gdb stops controlling a thread after "Remote 'g' packet reply is too long: ..." error message
Date: Tue, 12 Apr 2016 13:37:00 -0000 [thread overview]
Message-ID: <570CFA04.3070109@codesourcery.com> (raw)
In-Reply-To: <CAGHpTBLM5r5xVWzxYv=qZpRz_o-d9=gp_yg+RSYqoEXFBywgfQ@mail.gmail.com>
On 04/12/2016 12:16 AM, Orgad Shaneh wrote:
> Hi,
>
> On Tue, Apr 12, 2016 at 12:19 AM, Luis Machado
> <lgustavo@codesourcery.com> wrote:
>> Hi,
>>
>> On 04/10/2016 09:49 AM, Orgad Shaneh wrote:
>>>
>>> Please review the attached patch. It was inspired by the patch
>>> attached to the bug report.
>>
>>
>> Usually, when you receive that message from GDB it because your target
>> reported an incorrect register set as a 'g' reply.
>>
>> The correct solution is to fix your remote target to reply the proper
>> register set.
>>
>> From the description, it sounds like QEMU needs to be adjusted.
>>
>
> Thanks for your reply.
>
> I don't use QEMU. I did not describe my use case in the bug report,
> did just now.
>
I got that from the bug report.
> I got this message when I tried to remotely debug a
> mips64-octeon-linux gdbserver 6.8 with GDB >= 7.5.
>
> GDB <= 7.4.1 works well, but with 7.5 and up I receive this message
> and the debugger stops functioning.
>
I suppose GDB 7.5 is slightly incompatible with older gdbserver versions.
What kind of target description does gdbserver return in this case (set
debug remote 1)?
next prev parent reply other threads:[~2016-04-12 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 14:49 Orgad Shaneh
2016-04-11 21:19 ` Luis Machado
2016-04-12 5:16 ` Orgad Shaneh
2016-04-12 13:37 ` Luis Machado [this message]
2016-04-13 5:43 ` Orgad Shaneh
2016-04-13 19:11 ` Luis Machado
2016-04-13 20:07 ` Orgad Shaneh
2016-04-13 20:27 ` Pedro Alves
2016-04-13 20:52 ` Orgad Shaneh
2016-04-13 21:57 ` Pedro Alves
2016-04-14 8:33 ` Orgad Shaneh
2016-04-14 9:07 ` Orgad Shaneh
2016-04-14 9:22 ` Pedro Alves
2016-04-14 9:39 ` Orgad Shaneh
2016-04-14 9:47 ` Pedro Alves
2016-04-14 21:21 ` Maciej W. Rozycki
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=570CFA04.3070109@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=orgads@gmail.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