From: Pedro Alves <palves@redhat.com>
To: Orgad Shaneh <orgads@gmail.com>
Cc: Luis Machado <lgustavo@codesourcery.com>,
gdb-patches@sourceware.org,
"Maciej W. Rozycki" <macro@linux-mips.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:47:00 -0000 [thread overview]
Message-ID: <570F6738.1010404@redhat.com> (raw)
In-Reply-To: <CAGHpTB+1vzHu=-AQhDRK808HiiM41wc+60UpFJXK8XoMe_ApMA@mail.gmail.com>
On 04/14/2016 10:39 AM, Orgad Shaneh wrote:
> On Thu, Apr 14, 2016 at 12:22 PM, Pedro Alves <palves@redhat.com> wrote:
>> On 04/14/2016 10:06 AM, Orgad Shaneh wrote:
>>
>>> 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.
>>
>> Since you can build gdb now, you should be able to use "git bisect"
>> to find the culprit.
>>
>> Thanks,
>> Pedro Alves
>>
>
> Good point. The first bad commit is 1faeff08.
>
Thanks. That's:
Author: Maciej W. Rozycki <macro@linux-mips.org>
AuthorDate: Thu Mar 1 22:19:48 2012 +0000
...
* mips-tdep.c (mips_generic_reg_names): Remove trailing null
strings.
(mips_tx39_reg_names): Likewise.
(mips_linux_reg_names): New array of register names for Linux
targets.
(mips_register_name): Check for a null pointer in
mips_processor_reg_names and return an empty string.
(mips_register_type): Exclude embedded registers for the IRIX
and Linux ABIs.
(mips_pseudo_register_type): Likewise. Use dynamic numbers to
refer to FP registers, LO, HI, BadVAddr, Cause and PC. Handle
DSP registers.
(mips_stab_reg_to_regnum): Handle DSP accumulators.
(mips_dwarf_dwarf2_ecoff_reg_to_regnum): Likewise.
(mips_gdbarch_init): Likewise. Initialize internal register
indices for the Linux ABI. Use dynamic numbers to refer to
registers, as applicable, while parsing the target description.
Maciej, see https://sourceware.org/ml/gdb-patches/2016-04/msg00310.html .
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-04-14 9:47 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
2016-04-14 9:22 ` Pedro Alves
2016-04-14 9:39 ` Orgad Shaneh
2016-04-14 9:47 ` Pedro Alves [this message]
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=570F6738.1010404@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=macro@linux-mips.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