From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32717 invoked by alias); 11 Dec 2008 20:39:11 -0000 Received: (qmail 32706 invoked by uid 22791); 11 Dec 2008 20:39:11 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 11 Dec 2008 20:38:35 +0000 Received: (qmail 28110 invoked from network); 11 Dec 2008 20:38:34 -0000 Received: from unknown (HELO orlando.local) (pedro@127.0.0.2) by mail.codesourcery.com with ESMTPA; 11 Dec 2008 20:38:34 -0000 From: Pedro Alves To: gdb-patches@sourceware.org Subject: Re: [commit] make step_1 use step_once Date: Thu, 11 Dec 2008 20:39:00 -0000 User-Agent: KMail/1.9.10 References: <200812112035.27148.pedro@codesourcery.com> In-Reply-To: <200812112035.27148.pedro@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812112038.33124.pedro@codesourcery.com> X-IsSubscribed: yes 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: 2008-12/txt/msg00211.txt.bz2 On Thursday 11 December 2008 20:35:26, Pedro Alves wrote: > Hi guys, > > This makes step_1 use step_once in the sync case as well to reduce > code (and logic) duplication. > > I found out when moving patches between trees here that I was doing > essentially what Daniel had already done in his pending inline frame > support patch set, so I split and merged both. Any new bug is > of course credited to yours truly. Daniel, I hope you don't mind me > doing this. > Argh, the ChangeLog entry I commited was this one, not what in the patch: 2008-12-11 Daniel Jacobowitz Pedro Alves * infcmd.c (step_1): Use step_once in the synchronous case too. (step_1_continuation): Wrap line. (step_once): Adjust comment. Only install the continuation in async mode. > Tested on x86-64-unknown-linux-gnu sync/async, and checked in. > -- Pedro Alves