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: reverse execution part of the manual is written backwards

From: Paul Eggert <eggert at cs dot ucla dot edu>
To: Pedro Alves <palves at redhat dot com>, Eli Zaretskii <eliz at gnu dot org>
Cc: gdb-patches at sourceware dot org
Date: Sun, 21 Apr 2019 23:50:22 -0700
Subject: Re: reverse execution part of the manual is written backwards
References: <5fbd40b5-7887-1000-3457-75190a5d96c0@cs.ucla.edu> <51cb91ba-6bcd-3de9-43d4-c766e2737c88@redhat.com> <831s297vwi.fsf@gnu.org> <111cf816-c27c-fe5d-7cb8-31375ad1cbc2@redhat.com>

Pedro Alves wrote:

How about this?

 From ed99ed89bf0d06edf844eaa018619d617b9bb99b Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Thu, 11 Apr 2019 16:03:33 +0100
Subject: [PATCH] Improve reverse debugging docs

	* gdb.texinfo (Reverse Execution): Mention and xref process record
	and replay.  Mention remote and system emulators.
	(Process Record and Replay): List supported architectures.
	Mention that "record btrace" is only supported on Intel
	processors.


Thanks, that patch looks good. Would you please install it?

Follow-Ups:
- Re: reverse execution part of the manual is written backwards
  - From: Pedro Alves

References:
- reverse execution part of the manual is written backwards
  - From: Paul Eggert
- Re: reverse execution part of the manual is written backwards
  - From: Pedro Alves
- Re: reverse execution part of the manual is written backwards
  - From: Eli Zaretskii
- Re: reverse execution part of the manual is written backwards
  - From: Pedro Alves

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