Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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:39:00 -0000	[thread overview]
Message-ID: <CAGHpTB+1vzHu=-AQhDRK808HiiM41wc+60UpFJXK8XoMe_ApMA@mail.gmail.com> (raw)
In-Reply-To: <570F613A.8060708@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 515 bytes --]

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.

Bisect log attached.

- Orgad

[-- Attachment #2: bisect.log --]
[-- Type: application/octet-stream, Size: 2754 bytes --]

git bisect start
# good: [66a5c7c17c5f2afb94e0eae4a7de6bb83eaeab62] NEWS: Change "since GDB 7.3.1" into "in GDB 7.4".
git bisect good 66a5c7c17c5f2afb94e0eae4a7de6bb83eaeab62
# bad: [3c2f71b3160efd230669cbb53d77178c23403aea] Update GDB version number in version.in
git bisect bad 3c2f71b3160efd230669cbb53d77178c23403aea
# bad: [3c2f71b3160efd230669cbb53d77178c23403aea] Update GDB version number in version.in
git bisect bad 3c2f71b3160efd230669cbb53d77178c23403aea
# good: [c5012cd8d53be0c5a3b0b4ae2a054b0a3dadbca2] bfd/ 2011-12-13  Tristan Gingold  <gingold@adacore.com>
git bisect good c5012cd8d53be0c5a3b0b4ae2a054b0a3dadbca2
# bad: [ece0061f93a5a99e3f5b063d271267b6414cd129] 2012-04-02  Tristan Gingold  <gingold@adacore.com>
git bisect bad ece0061f93a5a99e3f5b063d271267b6414cd129
# good: [32d79e68186ae2d123ec2f100c40440fe2951c7e] 	* ld-elf/linkoncerdiff.d: Don't run for hppa64-hpux. 	* ld-elf/pr11304a.s: Always have whitespace before directives. 	* ld-elf/pr11304b.s: Likewise. 	* ld-selective/selective.exp: Test m68hc1* variant of m6811, m6812. 	* lib/ld-lib.exp: Likewise, and vice versa.
git bisect good 32d79e68186ae2d123ec2f100c40440fe2951c7e
# bad: [1b7c1b10aaa8bd6eec6555ac64fd070c43a45706] 2012-03-06  Pedro Alves  <palves@redhat.com>
git bisect bad 1b7c1b10aaa8bd6eec6555ac64fd070c43a45706
# good: [644cebc98ce121ef7e6a8c0d1867ae01e936b41b] 2012-02-27  Pedro Alves  <palves@redhat.com>
git bisect good 644cebc98ce121ef7e6a8c0d1867ae01e936b41b
# bad: [263689d88a2cbcedb42e925400e88f71ddb81698] Fix typo in frame.h:read_frame_register_unsigned function description.
git bisect bad 263689d88a2cbcedb42e925400e88f71ddb81698
# good: [8ba85d852669213fb96aca1cc5449d3789c315e2] Import gnulib's latest update-copyright script...
git bisect good 8ba85d852669213fb96aca1cc5449d3789c315e2
# good: [ad5f7d6ef7055f46c1734b9862bd156c355a8b3d] 2012-03-01  Pedro Alves  <palves@redhat.com>
git bisect good ad5f7d6ef7055f46c1734b9862bd156c355a8b3d
# good: [9340a6c0be7b3c4ed008c16c42a9da1350b42c10] 2012-03-01  Pedro Alves  <palves@redhat.com>
git bisect good 9340a6c0be7b3c4ed008c16c42a9da1350b42c10
# good: [70221824e31ba9c4e8cc710f11c986c37c947310] 2012-03-01  Pedro Alves  <palves@redhat.com>
git bisect good 70221824e31ba9c4e8cc710f11c986c37c947310
# good: [f3b4f45c3398591eed0bf54bb2a51266aa8a2c4a] 2012-03-01  Pedro Alves  <palves@redhat.com>
git bisect good f3b4f45c3398591eed0bf54bb2a51266aa8a2c4a
# bad: [a385295e2c80123b85dab47754e049e418925484] 	* mips-tdep.c (mips32_bc1_pc): New function. 	(mips32_next_pc): Handle BC1ANY2F, BC1ANY2T, BC1ANY4F, BC1ANY4T, 	BPOSGE32 and BPOSGE64 instructions. 	(deal_with_atomic_sequence): Likewise. 	(mips32_instruction_has_delay_slot): Likewise.
git bisect bad a385295e2c80123b85dab47754e049e418925484

  reply	other threads:[~2016-04-14  9:39 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 [this message]
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+1vzHu=-AQhDRK808HiiM41wc+60UpFJXK8XoMe_ApMA@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