public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Simon Marchi <simon.marchi@efficios.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: make gdb_breakpoint and runto use options
Date: Tue, 29 Nov 2022 16:41:54 -0500	[thread overview]
Message-ID: <15b32e67-5431-b489-379e-5e4d83775ec0@polymtl.ca> (raw)
In-Reply-To: <20221129213907.108082-1-simon.marchi@efficios.com>

On 11/29/22 16:39, Simon Marchi wrote:
> From: Simon Marchi <simon.marchi@polymtl.ca>
> 
> Change gdb_breakpoint and runto to use options (parsed with
> parse_options) instead of simply looking up keywords in args.  It is
> more robust what we generally prefer now, I believe.
> 
> runto passes its extra args directly to gdb_breakpoint, so it's easier
> to change both at the same time.
> 
> Change-Id: Id1017345786bdf5940953521e67b291f065b9966

Please disregard this one.  I sent the wrong patch, this one is part of a series
that isn't ready yet.

Simon


      reply	other threads:[~2022-11-29 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29 21:39 Simon Marchi
2022-11-29 21:41 ` Simon Marchi [this message]

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=15b32e67-5431-b489-379e-5e4d83775ec0@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).