public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Simon Marchi <simon.marchi@efficios.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/9] Fix gdb.dap/basic-dap.exp for PIE
Date: Mon, 16 Jan 2023 11:07:41 -0500	[thread overview]
Message-ID: <36f2e8b0-b5e4-7f0f-8bf0-e4e3f46862f5@simark.ca> (raw)
In-Reply-To: <20230106185729.42372-1-simon.marchi@efficios.com>

Ping.

On 1/6/23 13:57, Simon Marchi via Gdb-patches wrote:
> The last patch of this series fixes a FAIL I get in
> gdb.dap/basic-dap.exp.  The rest of the patches are small improvements I
> made to lib/dap-support.exp that helped me get there.
> 
> Simon Marchi (9):
>   gdb/testsuite/dap: use gdb_assert in gdb.dap/basic-dap.exp
>   gdb/testsuite/dap: prefix some procs with _
>   gdb/testsuite/dap: write requests to gdb.log
>   gdb/testsuite/dap: make dap_request_and_response not catch / issue
>     test result
>   gdb/testsuite/dap: remove catch from dap_read_event
>   gdb/testsuite/dap: pass around dicts instead of ton objects
>   gdb/testsuite/dap: rename dap_read_event to
>     dap_wait_for_event_and_check
>   gdb/testsuite/dap: make dap_wait_for_event_and_check return preceding
>     messages
>   gdb/testsuite/dap: fix gdb.dap/basic-dap.exp disassembly test for PIE
> 
>  gdb/testsuite/gdb.dap/basic-dap.exp |  73 ++++++++++-------
>  gdb/testsuite/lib/dap-support.exp   | 121 ++++++++++++++--------------
>  2 files changed, 102 insertions(+), 92 deletions(-)
> 

  parent reply	other threads:[~2023-01-16 16:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 18:57 Simon Marchi
2023-01-06 18:57 ` [PATCH 1/9] gdb/testsuite/dap: use gdb_assert in gdb.dap/basic-dap.exp Simon Marchi
2023-01-25 21:58   ` Tom Tromey
2023-01-06 18:57 ` [PATCH 2/9] gdb/testsuite/dap: prefix some procs with _ Simon Marchi
2023-01-25 21:59   ` Tom Tromey
2023-01-06 18:57 ` [PATCH 3/9] gdb/testsuite/dap: write requests to gdb.log Simon Marchi
2023-01-25 21:59   ` Tom Tromey
2023-01-25 22:01   ` Tom Tromey
2023-01-26  3:01     ` Simon Marchi
2023-01-06 18:57 ` [PATCH 4/9] gdb/testsuite/dap: make dap_request_and_response not catch / issue test result Simon Marchi
2023-01-06 18:57 ` [PATCH 5/9] gdb/testsuite/dap: remove catch from dap_read_event Simon Marchi
2023-01-06 18:57 ` [PATCH 6/9] gdb/testsuite/dap: pass around dicts instead of ton objects Simon Marchi
2023-01-25 22:04   ` Tom Tromey
2023-01-26  3:29     ` Simon Marchi
2023-01-26 14:55       ` Tom Tromey
2023-01-06 18:57 ` [PATCH 7/9] gdb/testsuite/dap: rename dap_read_event to dap_wait_for_event_and_check Simon Marchi
2023-01-06 18:57 ` [PATCH 8/9] gdb/testsuite/dap: make dap_wait_for_event_and_check return preceding messages Simon Marchi
2023-01-06 18:57 ` [PATCH 9/9] gdb/testsuite/dap: fix gdb.dap/basic-dap.exp disassembly test for PIE Simon Marchi
2023-01-25 22:10   ` Tom Tromey
2023-01-26  3:40     ` Simon Marchi
2023-01-26 15:08       ` Tom Tromey
2023-01-26 20:21         ` Simon Marchi
2023-01-16 16:07 ` Simon Marchi [this message]
2023-01-25 22:10   ` [PATCH 0/9] Fix gdb.dap/basic-dap.exp " Tom Tromey
2023-01-26 20:22     ` Simon Marchi

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=36f2e8b0-b5e4-7f0f-8bf0-e4e3f46862f5@simark.ca \
    --to=simark@simark.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).