Re: PR13984 - gdb stops controlling a thread after "Remote 'g' packet reply is too long: ..." error message

Pedro Alves
2016-04-14T09:47:51Z

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