[qt/qt-creator/qt-creator]: Summary of bulk changes made

Git repository change summary for qt/qt-creator/qt-creator
Pushed by mirror-service into branch 'master'.
Changed from 785c71422877d93e1adb70f0a5d198d505ec394b to 7a8ceaeb0a963bcddb710a82c821ea20efc99a2c
Acknowledgement was received that this change introduces only existing code that has been pushed to another public open source repository.

This change contains the following new commits:

Git commit 2582a840c22109de3a717e978dd207d4281acc15 by hjk on 14/08/2026 at 06:10..
Qnx: Start the slog2 log follower without preamble round-trips

slog2InfoRecipe ran two preparatory commands on the device - an
existence probe and a launch-time query - before starting
"slog2info -w". That follower only reports entries logged after it
attaches; it does not replay the buffer. So every preceding round-trip
just widens the window in which early application output is lost, the
more so over a slow ssh-fallback connection.

Start the follower first. The launch-time filtering it fed was dead
code for "-w" (there are no pre-launch entries to skip) and is removed
along with it; a failure to start slog2info is still reported.

Assisted-by: Claude Code
Change-Id: I9539a51975ade27e6cfaf1121dd246103229ffd6
Reviewed-by: Marcus Tillmanns <[email protected]>
https://invent.kde.org/qt/qt-creator/qt-creator/-/commit/2582a840c22109de3a717e978dd207d4281acc15

Git commit 8597e111a8dd9da8bf8fae2237453820f1ece4da by hjk on 14/08/2026 at 06:10..
Qnx: Stop the run after the application exits

The run worker runs the application process in parallel with
slog2InfoRecipe, which follows the system log with "slog2info -w" and
never finishes on its own. With the group's default StopOnError policy
the run therefore never stopped once the application had exited: the
Application Output kept showing as running and no exit code was ever
reported.

Use stopOnSuccessOrError so the group finishes - cancelling the log
follower - as soon as the application process is done.

Amends 230b676516c091659430c4f24492c77a03ea29e0.

Assisted-by: Claude Code
Change-Id: I65d6c05880e0ed81da4db61796afe6603284d7e4
Reviewed-by: Marcus Tillmanns <[email protected]>
https://invent.kde.org/qt/qt-creator/qt-creator/-/commit/8597e111a8dd9da8bf8fae2237453820f1ece4da

Git commit 7a8ceaeb0a963bcddb710a82c821ea20efc99a2c by hjk on 14/08/2026 at 06:10..
BareMetal: Restore the pipe marker for OpenOCD pipe connections

In pipe startup mode the GDB server channel must be handed to gdb as
"target remote | <program> <args>"; the leading "|" is what makes gdb
launch the program and talk to it over its stdio. channelPipe() used to
prepend it, but it was dropped when the QUrl-based remote-channel
handling (which added the marker in the engine) was reverted, while the
sibling vgdb/valgrind case had its "|" restored. As a result OpenOCD
pipe mode emitted "target remote /path/openocd ..." and gdb failed with
a connection error, matching QTCREATORBUG-18316.

Restore the "|" in channelPipe(), consistent with the valgrind channel.

Amends d2b0b07e9d0f83cfbd686ffe3385eb09539dec80.

Fixes: QTCREATORBUG-18316
Assisted-by: Claude Code
Change-Id: Ie30255e69c08b4cb45f96068103dd961718b5b8f
Reviewed-by: Marcus Tillmanns <[email protected]>
https://invent.kde.org/qt/qt-creator/qt-creator/-/commit/7a8ceaeb0a963bcddb710a82c821ea20efc99a2c