This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Reverse Debugging, 1/5
- From: Daniel Jacobowitz <drow at false dot org>
- To: Michael Snyder <msnyder at vmware dot com>
- Cc: Joel Brobecker <brobecker at adacore dot com>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>, Pedro Alves <pedro at codesourcery dot com>, teawater <teawater at gmail dot com>
- Date: Mon, 6 Oct 2008 17:11:31 -0400
- Subject: Re: [RFA] Reverse Debugging, 1/5
- References: <48E3CCB6.4060501@vmware.com> <20081006203021.GA21853@adacore.com> <48EA7C75.7070703@vmware.com>
On Mon, Oct 06, 2008 at 02:00:37PM -0700, Michael Snyder wrote:
> It was a design choice.
>
> There were two choices:
> 1) modify target_resume (ops->to_resume), to add a direction
> parameter.
> 2) Add a to_set_direction target method.
>
> The first would have required modifying all existing targets,
> so I chose the second.
The problem is, we're now talking about a multi-process GDB. It's a
small step from there to one using multiple targets automatically. Is
core GDB going to have to do the juggling / bookkeeping to keep
direction in sync for all of them? The granularity will depend on the
backend...
If it's just a matter of changing the existing targets, then avoiding
that on a branch makes sense - but updating everything in the mainline
version makes sense too.
--
Daniel Jacobowitz
CodeSourcery