This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Check for truncated registers in process_g_packet

From: Simon Marchi <simon dot marchi at polymtl dot ca>
To: Yao Qi <qiyaoltc at gmail dot com>
Cc: Pedro Alves <palves at redhat dot com>, Lionel Flandrin <lionel at svkt dot org>, Simon Marchi <simon dot marchi at ericsson dot com>, gdb-patches at sourceware dot org
Date: Sat, 26 Aug 2017 00:49:40 +0200
Subject: Re: Check for truncated registers in process_g_packet
Authentication-results: sourceware.org; auth=none
References: <20161018111023.4hzeyfzzpaneyfds@localhost.localdomain> <33a1f569-995b-342a-dbb9-ea14ab377d1a@ericsson.com> <20161018160657.rdvxgcam3uibsgst@localhost.localdomain> <6f2568ee-7677-63e8-2d51-65ac531b3a84@redhat.com> <CAH=s-PM=2E-RHJeqDX=GVibaZP8s5mPmViFjOZnGCfqZ138JFQ@mail.gmail.com> <99a028d3486fedc258429c8c22e4777c@polymtl.ca>

On 2017-08-25 23:04, Simon Marchi wrote:

If I move the line mentioned above just after the follow_exec call,
gdb interprets the g reply with the right/new gdbarch, so the test
case works.  I don't know if it breaks anything else, but so far I
didn't find anything before that point that relied on stop_pc.  I sent
that change to the buildbot to check.


Hmm, this causes gdb.base/foll-exec-mode.exp to fail.

Follow-Ups:
- [PATCH 0/4] Try to fix the gdb.multi/multi-arch-exec.exp failure
  - From: Simon Marchi

References:
- Re: Check for truncated registers in process_g_packet
  - From: Yao Qi
- Re: Check for truncated registers in process_g_packet
  - From: Simon Marchi

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]