From: "Bouhaouel, Mohamed" <mohamed.bouhaouel@intel.com>
To: Pedro Alves <pedro@palves.net>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v3 09/11] infrun: with AS+NS, prefer process exit over thread exit
Date: Mon, 11 May 2026 11:58:15 +0000 [thread overview]
Message-ID: <IA1PR11MB71750C82BCB6EA1D7ED049CEE4382@IA1PR11MB7175.namprd11.prod.outlook.com> (raw)
In-Reply-To: <35c47df0-dcb9-4223-b183-31f30e90db36@palves.net>
Hi,
Thanks, Pedro for your feedback! This is the bug report I filed:
https://sourceware.org/bugzilla/show_bug.cgi?id=34142
--Mohamed
> -----Original Message-----
> From: Pedro Alves <pedro@palves.net>
> Sent: Friday, 8 May 2026 23:38
> To: Bouhaouel, Mohamed <mohamed.bouhaouel@intel.com>; gdb-
> patches@sourceware.org
> Subject: Re: [PATCH v3 09/11] infrun: with AS+NS, prefer process exit over
> thread exit
>
> Hi!
>
> On 2026-05-06 11:01, Bouhaouel, Mohamed wrote:
> > Hi Pedro,
> >
> > On Linux, with a remote non-stop target (AS on top of NS), the test you
> added
> > is failing! Isn't it supposed to pass in such scenario?
>
> It is, like _all_ tests are supposed to pass, old and new. :-) Sometimes new
> tests expose
> preexisting problems on some targets/ports, though.
>
> >
> > I see the following logs, without the "[Inferior ... exited normally]" message.
> >
> > Breakpoint 1, main () at /home/gta/sources/gdb-
> worktrees/upstream/gdb/testsuite/gdb.threads/step-over-process-exit.c:39
> > 39 alarm (30);
> > (gdb) p other_thread_exits = 0
> > $1 = 0
> > (gdb) PASS: gdb.threads/step-over-process-exit.exp: which=main: p
> other_thread_exits = 0
> > break 44
> > Breakpoint 2 at 0x555555555216: file /home/gta/sources/gdb-
> worktrees/upstream/gdb/testsuite/gdb.threads/step-over-process-exit.c, line
> 44.
> > (gdb) continue
> > Continuing.
> > [New Thread 18153.18154 (id 2)]
> >
> > Thread 1 "step-over-proce" hit Breakpoint 2, main () at
> /home/gta/sources/gdb-worktrees/upstream/gdb/testsuite/gdb.threads/step-
> over-process-exit.c:44
> > 44 exit (0); /* break here main */
> > (gdb) PASS: gdb.threads/step-over-process-exit.exp: which=main: continue
> to breakpoint: exit syscall
> > maint show target-non-stop
> > Whether the target is always in non-stop mode is on.
> > (gdb) next
> > [Thread 18153.18153 (id 1) exited]
> > warning: error removing breakpoint 0 at 0x555555555220
> > warning: error removing breakpoint 0 at 0x555555555220
> > warning: error removing breakpoint 0 at 0x555555555220
> > Remote communication error. Target disconnected: error while reading:
> Connection reset by peer.
> > (gdb) FAIL: gdb.threads/step-over-process-exit.exp: which=main: next
> >
> > To reproduce, simply run gdb.threads/step-over-process-exit.exp with:
> >
> > export GDBFLAGS="-ex \"maint set target-non-stop on\""
> >
>
> Could you file a bug about this, please?
>
> Pedro Alves
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2026-05-11 11:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 20:14 [PATCH v3 00/11] Windows non-stop mode Pedro Alves
2026-04-29 20:14 ` [PATCH v3 01/11] Windows gdb+gdbserver: Check whether DBG_REPLY_LATER is available Pedro Alves
2026-04-29 20:14 ` [PATCH v3 02/11] linux-nat: Factor out get_detach_signal code to common code Pedro Alves
2026-04-29 20:14 ` [PATCH v3 03/11] Windows GDB: make windows_thread_info be private thread_info data Pedro Alves
2026-04-29 20:15 ` [PATCH v3 04/11] Introduce windows_nat::event_code_to_string Pedro Alves
2026-04-29 20:15 ` [PATCH v3 05/11] Windows gdb: Add non-stop support Pedro Alves
2026-04-29 20:15 ` [PATCH v3 06/11] Windows gdb: Watchpoints while running (internal vs external stops) Pedro Alves
2026-04-29 20:15 ` [PATCH v3 07/11] Windows gdb: extra thread info => show exiting Pedro Alves
2026-04-29 20:15 ` [PATCH v3 08/11] Add gdb.threads/leader-exit-schedlock.exp Pedro Alves
2026-04-29 20:15 ` [PATCH v3 09/11] infrun: with AS+NS, prefer process exit over thread exit Pedro Alves
2026-05-06 10:01 ` Bouhaouel, Mohamed
2026-05-08 21:37 ` Pedro Alves
2026-05-11 11:58 ` Bouhaouel, Mohamed [this message]
2026-04-29 20:15 ` [PATCH v3 10/11] Windows gdb: Always non-stop (default to "maint set target-non-stop on") Pedro Alves
2026-04-29 20:15 ` [PATCH v3 11/11] Mention Windows non-stop support in NEWS Pedro Alves
2026-04-30 5:55 ` [PATCH v3 00/11] Windows non-stop mode Eli Zaretskii
2026-04-30 10:13 ` Pedro Alves
2026-04-30 11:14 ` Eli Zaretskii
2026-04-30 12:01 ` Pedro Alves
2026-04-30 14:15 ` [PATCH] Clarify "maint set target-non-stop" in GDB manual (Re: [PATCH v3 00/11] Windows non-stop mode) Pedro Alves
2026-04-30 15:09 ` Eli Zaretskii
2026-04-30 16:18 ` [PATCH v2] " Pedro Alves
2026-04-30 16:27 ` Eli Zaretskii
2026-04-30 16:33 ` Pedro Alves
2026-04-30 17:45 ` [PATCH v3 00/11] Windows non-stop mode Pedro Alves
2026-05-08 18:43 ` Tom Tromey
2026-05-08 21:27 ` Pedro Alves
2026-05-22 0:22 ` Pedro Alves
2026-06-02 19:00 ` Tom Tromey
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=IA1PR11MB71750C82BCB6EA1D7ED049CEE4382@IA1PR11MB7175.namprd11.prod.outlook.com \
--to=mohamed.bouhaouel@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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