Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>, gdb@sourceware.org
Subject: Re: Who uses gdbreplay?
Date: Thu, 12 Jun 2008 20:15:00 -0000	[thread overview]
Message-ID: <1213301731.3601.696.camel@localhost.localdomain> (raw)
In-Reply-To: <20080612200614.GA6572@caradoc.them.org>

On Thu, 2008-06-12 at 16:06 -0400, Daniel Jacobowitz wrote:
> On Thu, Jun 12, 2008 at 12:56:51PM -0700, Michael Snyder wrote:
> > Oh, absolutely.  No worries.
> > 
> > gdbreplay is elegant in its simplicity, I don't want to 
> > compromise that.  I'm actually working in rda.  
> 
> Ok, I think I've gotten turned around.  Were you talking about
> improvements to gdbreplay on the one hand and a separate program for
> traces?

I guess I'm talking about a separate program that does 
essentially a huge superset of gdbreplay's current functionality, 
using the same input logfile as is currently used by gdbreplay.

In a sense a replacement for gdbreplay, but the existing
gdbreplay doesn't have to go away, if it serves a purpose.

> It's kind of a shame you're working in rda.  I'm sure it's nice and
> all - but it never got contributed to the FSF, and I'm not entirely
> happy about new bits of GDB development using it because of that.
> It's still got RH copyright notices all over it.

Yeah, well -- show me an alternative.  Gdbserver?  Maybe.

In principle the stuff I'm writing could go into gdbserver
or some other debug-agent codebase.

This is an extension of a different project I was working on,
using rda.  It just occurred to me that I could make it use
the log files that are used by gdbreplay, and make them 
suddenly really useful.




  reply	other threads:[~2008-06-12 20:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 18:35 Michael Snyder
2008-06-12 18:55 ` Marc Khouzam
2008-06-12 19:07   ` Daniel Jacobowitz
2008-06-12 19:12   ` Michael Snyder
2008-06-12 19:19     ` Daniel Jacobowitz
2008-06-12 19:39       ` Michael Snyder
2008-06-12 19:47         ` Daniel Jacobowitz
2008-06-12 19:57           ` Michael Snyder
2008-06-12 20:06             ` Daniel Jacobowitz
2008-06-12 20:15               ` Michael Snyder [this message]
2008-06-12 20:24                 ` Daniel Jacobowitz
2008-06-12 20:56                   ` Michael Snyder
2008-06-12 19:28     ` Marc Khouzam
2008-06-12 19:44       ` Michael Snyder

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=1213301731.3601.696.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=marc.khouzam@ericsson.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