Re: [PATCH v2 00/47] Windows non-stop mode

Tom Tromey
2025-06-05T17:58:21Z

>>>>> "Pedro" == Pedro Alves <pedro@palves.net> writes:

Pedro> I've pushed the series to the users/palves/windows-non-stop-v2 branch
Pedro> on sourceware.org, for your convenience.

I merged this into the local tree and ran the internal AdaCore test
suite on Windows 2016.

There were three "failures".

One of them is actually an improvement, where the test works around a
current issue.

One of them seems to be a problem with the test. This test "attach"es
to a running process without a "file", and the test doesn't seem to
match the new output:

(gdb) attach 1228
Attaching to process 1228
[Switching to Thread 1228.0x580]
0x00007ffe3c756714 in ntdll!ZwDelayExecution ()
from C:\Windows\SYSTEM32\ntdll.dll

I'm not quite as sure about the last one. This test sets a couple of
breakpoints that have 'commands', where the commands delete the
breakpoint, like:

[ break main.adb:4 then ... ]
"silent",
'printf "Breakpoint hit #1.\\n"',
"clear main.adb:4",
"continue",
"end",

When running the expected output is seen but gdb says:

(gdb) run
Starting program: C:\[...]
Breakpoint hit #1.
Breakpoint hit #2.
No unwaited-for children left.

It's that last line that causes the problem. The test expects an "exit
notification", which is kind of complicated in this test suite, but I
think for native testing boils down to a message like "[Inferior
... exited ...]".

I see this "unwaited-for" text in infrun.c. But I wonder if this is
really intended.

thanks,
Tom