From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id cA+rFSXSqWIyWAIAWB0awg (envelope-from ) for ; Wed, 15 Jun 2022 08:35:49 -0400 Received: by simark.ca (Postfix, from userid 112) id 3B20F1E224; Wed, 15 Jun 2022 08:35:49 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=AjhmB2Ei; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id C50A21E15D for ; Wed, 15 Jun 2022 08:35:48 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 5E71A3839C7F for ; Wed, 15 Jun 2022 12:35:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5E71A3839C7F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1655296548; bh=RTFRfgFuHMoersp/l13LZWoEYMekjI3/LCIUfUoJTIE=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=AjhmB2EiUq6v0wFIeNRUIGPGEA0XMKT4p2xgnWxtkiCwqXLdKmUw0m9wfemo+iRnQ pKHBRIPX6Yzkx+BUNGDak9XTPt8saPzbD14qPn7HyV726N7zuTMSJzzuxYHA0w/6SJ cTT4rHgDsz8awTDtv5XCLF7UJqH8goBIhRQoDmtQ= Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) by sourceware.org (Postfix) with ESMTPS id A2F51385274E for ; Wed, 15 Jun 2022 12:35:21 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A2F51385274E Received: by mail-yb1-xb33.google.com with SMTP id t32so20196307ybt.12 for ; Wed, 15 Jun 2022 05:35:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=RTFRfgFuHMoersp/l13LZWoEYMekjI3/LCIUfUoJTIE=; b=BWc6IZZggM0bx9s4Zx8T78n7db9luFZIZE1xi3tph/naclE87ZZhBwtXX1tNDfZfKe BzZ3AA/ttnsBtlLN4H2TXRYUMEMsuSGASd3GVP8dEAS7pwnJhBmyu1fELR2GE4E3CJJb L9n1/WVGZeeIV/vbE44k9BeHdCFphaihVkqp2LbZ8UskzCd3Whprp/igFirKarhu4nLk ybM54fm0b8gg1ELiH8OgjtA2moUJXb/3zOC3jEgLHlydKHm45syz3i7TyX5fHAi5nTYj XaOLlAo5CS3OVX9cF7RmUc55t+YFQCOSmrZjysRMM5dzGvMM0R6tvP4xpl/w0+gHoH/t rJkg== X-Gm-Message-State: AJIora95IB6qOGnZeDX8IKKm9Rw+auOkeUDHIJwBmR4fgOuT/2azTVNP Tdfb1hGZ0KB7OHM+ZH+OjKpkPMpFgLNGv97OuAWYlA== X-Google-Smtp-Source: AGRyM1uEbuJHPHGzSJvhI/A517e0ZAjgt5QQY6pV03zBdJANzJ888XL7eKnszlj3bsKvbk4d8JSOPMsCcMb/QJbYwuU= X-Received: by 2002:a05:6902:1106:b0:665:4422:91dc with SMTP id o6-20020a056902110600b00665442291dcmr7935200ybu.200.1655296520814; Wed, 15 Jun 2022 05:35:20 -0700 (PDT) MIME-Version: 1.0 References: <040e723a-1f8b-3fb2-a076-85664243513f@redhat.com> In-Reply-To: <040e723a-1f8b-3fb2-a076-85664243513f@redhat.com> Date: Wed, 15 Jun 2022 08:34:41 -0400 Message-ID: Subject: Re: [RFC] Change displayed line when execution direction is reversed To: Bruno Larsen Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Christian Biesinger via Gdb Reply-To: Christian Biesinger Cc: Reuben Thomas via Gdb Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" My personal opinion: In general, the state of the program when gdb is stopped is the state at the start of the displayed line (I concede that it gets more complicated when "step"ping) This change would make it so the state is the state at the end of the displayed line. I think that could be confusing? Perhaps could be mitigated by printing a message explaining that in some way. Christian On Wed, Jun 15, 2022 at 8:26 AM Bruno Larsen via Gdb w= rote: > > Hello all, > > I was doing some reverse debugging and noticed that setting the execution= direction to reverse does not change how GDB displays lines. The problem w= ith this is that the user doesn't see what will be executed if a step is ta= ken, which makes the user experience quite annoying. How would the communit= y feel if GDB printed the previous line, instead of current line, when the = execution direction is reversed? > > Sorry if this is the wrong list. It didn't feel like a bug, and I don't h= ave a patch yet, so this felt like the best place to send. > -- > Cheers! > Bruno Larsen >