From: Bruno Larsen <blarsen@redhat.com>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "simark@simark.ca" <simark@simark.ca>
Subject: Re: [PATCH v2] gdb/infrun: do not restart a stepped thread if not running (was: gdb/infrun: reset thread control's step info in end_stepping_range)
Date: Thu, 22 Jun 2023 09:39:56 +0200 [thread overview]
Message-ID: <1995161e-aade-a5f5-a254-3b9a82ec0dea@redhat.com> (raw)
In-Reply-To: <DM4PR11MB7303DF406FC619691A37965BC422A@DM4PR11MB7303.namprd11.prod.outlook.com>
On 22/06/2023 09:02, Aktemur, Tankut Baris wrote:
> On Wednesday, June 21, 2023 2:35 PM, Bruno Larsen wrote:
>>> Regression-tested on X86_64 Linux using the default, native-gdbserver,
>>> and native-extended-gdbserver board files.
>> Hi Tankut!
>>
>> Thanks for working on this. I don't see any regressions, but the test
>> you added doesn't seem to fail before your change. Does it not work with
>> the default options for the testsuite?
> Hi Bruno,
>
> Thanks for checking. The bug condition is triggered when the target is all-stop.
> Could you please try with --target_board=native-extended-gdbserver ?
> Then you should see
>
> FAIL: gdb.multi/detach-stepi.exp: detach inferior 1
>
> === gdb Summary ===
>
> # of expected passes 8
> # of unexpected failures 1
>
Ah got it! I have tested and it fixes the problem :)
Tested-By: Bruno Larsen <blarsen@redhat.com>
--
Cheers,
Bruno
next prev parent reply other threads:[~2023-06-22 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 15:24 Tankut Baris Aktemur
2023-06-21 12:35 ` Bruno Larsen
2023-06-22 7:02 ` Aktemur, Tankut Baris
2023-06-22 7:39 ` Bruno Larsen [this message]
2023-06-22 8:01 ` Aktemur, Tankut Baris
2023-11-21 20:00 ` Aktemur, Tankut Baris
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=1995161e-aade-a5f5-a254-3b9a82ec0dea@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tankut.baris.aktemur@intel.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).