This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFA] Reverse debugging, part 3/3: user interface / docs
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Michael Snyder <msnyder at redhat dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Tue, 18 Apr 2006 12:15:40 +0300
- Subject: Re: [RFA] Reverse debugging, part 3/3: user interface / docs
- References: <442DAAD9.6080509@redhat.com> <ufykxa1jq.fsf@gnu.org> <44442877.1060401@redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Mon, 17 Apr 2006 16:44:55 -0700
> From: Michael Snyder <msnyder@redhat.com>
> CC: gdb-patches@sources.redhat.com
>
> Please see revised patch, attached.
> OK now?
The corrections you made are okay, but you left two of my suggestions
unhandled, please at least explain why.
> >>+ Behavior of
> >>+ asynchronous signals depends on the target environment.
> >
> >
> > This is too vague. Can we at least mention the possible behaviors, or
> > just the most common/expected ones? The reader should get some idea
> > of what might happen.
You didn't change anything in response to this comment.
> >>+ Run the program backward until control reaches the start of a
> >>+ different source line
> >
> >
> > Isn't it better to say
> >
> > Run the program backwards until control reaches the first instruction
> > of a different source line
> >
> > ? In any case, "backwards", not "backward".
You left "backward" in the text.