public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/24788] Add support for 'reverse-until'
Date: Wed, 29 Nov 2023 09:37:44 +0000	[thread overview]
Message-ID: <bug-24788-4717-t58udRiChT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24788-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=24788

Guinevere Larsen <blarsen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |blarsen at redhat dot com
           Keywords|                            |good-first-bug
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2023-11-29

--- Comment #1 from Guinevere Larsen <blarsen at redhat dot com> ---
Right now you can use 'set exec-direction reverse' and then 'until <line>' to
execute the inferior until a desired line, but if you try to use 'until' with
no arguments, it will run to the end of the function (or execution history)
instead of leaving a loop.

Meaning this is effectively 2 bugs: we need to fix the execution with no
parameters, and we need a new command that will automagically set the execution
direction and reset- it afterwards (like 'reverse-next').

Ideally, these problems should be solved in order, so it doesn't feel like we
have a "half-baked" feature, but if someone were to submit a patch that makes
until error out on the first condition (executing in reverse and called with no
arguments) and adds the command, I think it would already be an improvement
over current behaviour.

Seeing as this new command shouldn't be too difficult to implement, I'm marking
this as a good-first-bug.

I filed a second bug for the 'until' changes, 
https://sourceware.org/bugzilla/show_bug.cgi?id=31094

-- 
You are receiving this mail because:
You are on the CC list for the bug.

       reply	other threads:[~2023-11-29  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-24788-4717@http.sourceware.org/bugzilla/>
2023-11-29  9:37 ` blarsen at redhat dot com [this message]
2024-05-24 20:34 ` blarsen at redhat dot com

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=bug-24788-4717-t58udRiChT@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).