From: Orgad Shaneh <orgads@gmail.com>
To: Luis Machado <lgustavo@codesourcery.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: Wed, 13 Apr 2016 20:07:00 -0000 [thread overview]
Message-ID: <CAGHpTB+dZ3a86nFFN8CAyTxzTBMk6eReWZpg03HYVqQO8-TVyA@mail.gmail.com> (raw)
In-Reply-To: <570E99DC.8080902@codesourcery.com>
On Wed, Apr 13, 2016 at 10:11 PM, Luis Machado
<lgustavo@codesourcery.com> wrote:
>
> On 04/13/2016 12:43 AM, Orgad Shaneh wrote:
>>>>
>>>> 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)?
>>
>>
>> Full log attached. Thanks for your help.
>>
>> - Orgad
>>
>
> Strange. If this is gdbserver 6.8, it should've replied to the qSupported packet? That one was added in 6.6.
Hi,
Sorry, my fault. The gdbserver is GNU gdb 6.5 Cavium Networks Version:
1_7_0, build 45
gdbserver 6.8 is in Cavium SDK2. I don't know if it works with recent GDB.
- Orgad
next prev parent reply other threads:[~2016-04-13 20:07 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
2016-04-13 5:43 ` Orgad Shaneh
2016-04-13 19:11 ` Luis Machado
2016-04-13 20:07 ` Orgad Shaneh [this message]
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=CAGHpTB+dZ3a86nFFN8CAyTxzTBMk6eReWZpg03HYVqQO8-TVyA@mail.gmail.com \
--to=orgads@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.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