public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Bruno Larsen <blarsen@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3] [gdb/testsuite] test a function call by hand from pretty printer
Date: Thu, 24 Mar 2022 10:18:57 -0400	[thread overview]
Message-ID: <8ecf9cc1-452a-b9f9-d53a-f35af1a0dc29@simark.ca> (raw)
In-Reply-To: <853f9e05-c815-d04c-371c-0fb1f31df2f2@redhat.com>

> Oh sorry, I didn't think about that. My thinking was that this looked
> like a pretty complex issue, so I could at least get some sort
> conversation going in case anyone knew how to fix the problem, and
> could help me find the origin of the problems. It doesn't test
> anything new that doesn't fail, but unfortunately, I had already
> pushed the change when your email arrived. If you want to remove it
> until I have a fix, I understand it. Sorry again.

Ok, I'll remove the test and attach it to the bug.  This will help bring
back my little CI closer to being green.

Simon

      reply	other threads:[~2022-03-24 14:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 18:57 [PATCH] [gdb/testsuite] test a function call by hand fron " Bruno Larsen
2022-02-27 12:39 ` Joel Brobecker
2022-02-28 12:13   ` Bruno Larsen
2022-03-06 10:43     ` Joel Brobecker
2022-03-07 13:09 ` [PATCH v2] " Bruno Larsen
2022-03-13  6:13   ` Joel Brobecker
2022-03-14 20:39 ` [PATCH v3] [gdb/testsuite] test a function call by hand from " Bruno Larsen
2022-03-19 14:41   ` Joel Brobecker
2022-03-21 20:21   ` Simon Marchi
2022-03-23 15:37     ` Bruno Larsen
2022-03-24 14:18       ` 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=8ecf9cc1-452a-b9f9-d53a-f35af1a0dc29@simark.ca \
    --to=simark@simark.ca \
    --cc=blarsen@redhat.com \
    --cc=gdb-patches@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).