From: Orgad Shaneh <orgads@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: Luis Machado <lgustavo@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: PR13984 - gdb stops controlling a thread after "Remote 'g' packet reply is too long: ..." error message
Date: Thu, 14 Apr 2016 09:07:00 -0000 [thread overview]
Message-ID: <CAGHpTBLAuUi5WdtFdbuVGav8GmQCA=aP=F+88fXsBRTKRvnCxQ@mail.gmail.com> (raw)
In-Reply-To: <CAGHpTB+y=1Rst7H9BsSX_enxraXAy_YpzPYRSCfoa=8QXvEM-w@mail.gmail.com>
On Thu, Apr 14, 2016 at 11:33 AM, Orgad Shaneh <orgads@gmail.com> wrote:
> On Thu, Apr 14, 2016 at 12:57 AM, Pedro Alves <palves@redhat.com> wrote:
>>> gdb-remote-7.6 is the output of 7.6 Cavium version, which doesn't.
>>
>> TBC, does this happen with current FSF master against old (unpatched)
>> FSF 7.4 gdbserver? This might be due to local Cavium patches...
>
> No. It works as expected.
>
> I tried compiling FSF 6.5 for mips64-octeon-linux-gnu host,
>
> configured using ./configure --host=mips64-octeon-linux-gnu
> --target=mips64-octeon-linux-gnu
>
> It works fine with 7.4, but uses the host's gcc with 6.5...
Ok, autoconf helped. FSF gdbserver 6.5 has the same issue when the gdb
client is >=7.5: "Remote 'g' packet reply is too long".
So this doesn't seem to be related to Cavium patches.
- Orgad
next prev parent reply other threads:[~2016-04-14 9: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
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 [this message]
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='CAGHpTBLAuUi5WdtFdbuVGav8GmQCA=aP=F+88fXsBRTKRvnCxQ@mail.gmail.com' \
--to=orgads@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=palves@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