Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Reverse debugging, part 2/3: core interface
Date: Sat, 01 Apr 2006 16:24:00 -0000	[thread overview]
Message-ID: <u4q1d9scj.fsf@gnu.org> (raw)
In-Reply-To: <20060401161016.GA23216@nevyn.them.org> (message from Daniel 	Jacobowitz on Sat, 1 Apr 2006 11:10:17 -0500)

> Date: Sat, 1 Apr 2006 11:10:17 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
> 
> On Sat, Apr 01, 2006 at 03:34:39PM +0300, Eli Zaretskii wrote:
> > In addition, I think "Run back to call of FOO" is not very clear.  I
> > wanted to suggest "Run to entry to FOO", but then I realized it would
> > be a lie: we do back up past the entry, to the instruction that
> > actually calls the function we are in, right?  Perhaps "Run back to
> > before the call to FOO" is better, even though it is wordier?
> 
> How about "Run back to call site of FOO"?  That's a pretty clear term.

Fine with me.

> > > ! 	  if (debug_infrun)
> > > ! 	    fprintf_unfiltered (gdb_stdlog, 
> > > ! 				"infrun: stepped to a different function\n");
> > 
> > _() is missing around the message string (yes, I know it was missing
> > in the original code as well, but...).
> 
> I thought we'd decided not to translate debug messages.
> 
> But I can't remember for sure

Neither do I.

> Sounds to me like we need the Coding chapter of gdbint.texinfo to
> record decisions about this :-)

Why not?  Feel free to write it up.


  reply	other threads:[~2006-04-01 16:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <442DAA95.6050708@redhat.com>
2006-04-01 12:34 ` Eli Zaretskii
2006-04-01 16:10   ` Daniel Jacobowitz
2006-04-01 16:24     ` Eli Zaretskii [this message]
2006-04-17 23:42   ` Michael Snyder
2006-04-18  9:04     ` Eli Zaretskii
2006-04-20 16:00     ` Daniel Jacobowitz
2006-04-20 19:49       ` Michael Snyder
2006-04-20 19:52         ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u4q1d9scj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox