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: [PATCH] gdb.trace: Use g packet order in tfile_fetch_registers.

From: Marcin KoÅcielnicki <koriakin at 0x04 dot net>
To: Pedro Alves <palves at redhat dot com>
Cc: gdb-patches at sourceware dot org
Date: Wed, 10 Feb 2016 15:49:37 +0100
Subject: Re: [PATCH] gdb.trace: Use g packet order in tfile_fetch_registers.
Authentication-results: sourceware.org; auth=none
References: <56BB4101 dot 5050902 at redhat dot com> <1455113532-24235-1-git-send-email-koriakin at 0x04 dot net> <56BB4780 dot 8010908 at redhat dot com>

On 10/02/16 15:21, Pedro Alves wrote:

On 02/10/2016 02:12 PM, Marcin KoÅcielnicki wrote:

tfile_fetch_registers currently wrongly fetches registers using
gdb order instead of g packet order.  On x86_64 with AVX, this causes
problems with ymm*h and orig_rax registers: gdb has ymm*h first, while
g packet has orig_rax first.

gdb/ChangeLog:

	* tracefile-tfile.c (tfile_fetch_registers): Use g packet order
	instead of gdb order.

gdb/doc/ChangeLog:

	* gdb.texinfo (Trace File Format): Remove misleading information
	about register block ordering.
---
Removed misleading documentation bit.  OK to push now?


OK.

Thanks,
Pedro Alves


Thanks, pushed.

References:
- Re: [PATCH 3/4] gdb.trace: Use g packet order in tfile_fetch_registers.
  - From: Pedro Alves
- [PATCH] gdb.trace: Use g packet order in tfile_fetch_registers.
  - From: Marcin KoÅcielnicki
- Re: [PATCH] gdb.trace: Use g packet order in tfile_fetch_registers.
  - From: Pedro Alves

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