From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4017 invoked by alias); 3 Jan 2012 02:58:29 -0000 Received: (qmail 4008 invoked by uid 22791); 3 Jan 2012 02:58:28 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 03 Jan 2012 02:58:16 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id EE01E2BB06B; Mon, 2 Jan 2012 21:58:15 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tTDV-wNU9lMt; Mon, 2 Jan 2012 21:58:15 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 874BF2BB069; Mon, 2 Jan 2012 21:58:15 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 4A460145615; Tue, 3 Jan 2012 06:58:07 +0400 (RET) Date: Tue, 03 Jan 2012 02:58:00 -0000 From: Joel Brobecker To: Mike Frysinger Cc: Pedro Alves , gdb-patches@sourceware.org Subject: Re: [PATCH] gdbserver: install gdbreplay too Message-ID: <20120103025807.GE2730@adacore.com> References: <1325321888-5293-1-git-send-email-vapier@gentoo.org> <4F01A735.8080503@gmail.com> <201201022130.23597.vapier@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201201022130.23597.vapier@gentoo.org> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00072.txt.bz2 > aren't all users just developers in hiding ? ;) > > i can drop it if people prefer not to install it One thing I realized is that there doesn't appear to be any documentation for that program. So, I looked at the program code, and it says that it takes a log file of the remote and replays it. But the documentation seems to also be silent about how to produce that log file. How does it work? -- Joel