From: AdrianF <adrian.freihofer@siemens.com>
To: openembedded-core@lists.openembedded.org
Cc: Adrian Freihofer <adrian.freihofer@siemens.com>
Subject: [PATCH 3/9] devtool: ide-sdk: pre-select attach process with processFilter
Date: Sun, 6 Sep 2026 23:02:01 +0200 [thread overview]
Message-ID: <20260906210307.2793974-4-adrian.freihofer@siemens.com> (raw)
In-Reply-To: <20260906210307.2793974-1-adrian.freihofer@siemens.com>
From: Adrian Freihofer <adrian.freihofer@siemens.com>
The ATTACH launch config now uses the extended-remote protocol, which
makes cppdbg show a picker listing every process running on the
target. In modified-recipe mode the binary to attach to is already
known, so the picker is only extra clicking, and on a busy target it
can make finding the right process among unrelated ones tedious.
Set "processFilter" to a regex matching the deployed binary's path so
cppdbg pre-selects it instead of showing the full process list. This
is a recent cpptools feature; until it ships in a released cpptools,
cppdbg silently ignores it and falls back to showing the full
unfiltered process list.
Require cpptools version that supports processFilter
https://github.com/microsoft/vscode-cpptools/pull/14684
Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
---
meta/lib/oeqa/selftest/cases/devtool.py | 1 +
scripts/lib/devtool/ide_plugins/ide_code.py | 1 +
2 files changed, 2 insertions(+)
diff --git a/meta/lib/oeqa/selftest/cases/devtool.py b/meta/lib/oeqa/selftest/cases/devtool.py
index 3a407a5162..a4b7a83094 100644
--- a/meta/lib/oeqa/selftest/cases/devtool.py
+++ b/meta/lib/oeqa/selftest/cases/devtool.py
@@ -3569,6 +3569,7 @@ class DevtoolIdeSdkGccTests(DevtoolIdeSdkTests):
# from the process instead of killing it.
self.assertTrue(config.get("useExtendedRemote"), f"Configuration '{config['name']}' should use useExtendedRemote")
self.assertNotIn("cwd", config, f"Configuration '{config['name']}' should not set cwd in attach mode")
+ self.assertTrue(config.get("processFilter"), f"Configuration '{config['name']}' should use processFilter")
else:
self.fail(f"Configuration '{config['name']}' has unexpected request type: {config['request']}")
diff --git a/scripts/lib/devtool/ide_plugins/ide_code.py b/scripts/lib/devtool/ide_plugins/ide_code.py
index 937c63a4a5..6effbac654 100644
--- a/scripts/lib/devtool/ide_plugins/ide_code.py
+++ b/scripts/lib/devtool/ide_plugins/ide_code.py
@@ -387,6 +387,7 @@ class IdeVSCode(IdeBase):
# this configuration is generated. Stopping the session detaches
# from the process instead of killing it.
launch_config["useExtendedRemote"] = True
+ launch_config["processFilter"] = "(^| )%s( |$)" % cross_debug_config.binary.binary_path
else:
# cwd, environment and externalConsole configure the process the
# debugger starts, they are not part of the attach schema.
--
2.55.0
next prev parent reply other threads:[~2026-09-06 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 21:01 [PATCH 0/9] devtool: ide-sdk: bug fixes, do_install-through-bitbake, NFS deploy prep AdrianF
2026-09-06 21:01 ` [PATCH 1/9] devtool: ide-sdk: fix GDB loading stale libs instead of recipe's own build AdrianF
2026-09-06 21:02 ` [PATCH 2/9] oe-selftest: devtool ide-sdk: do not guess the slirp SSH port AdrianF
2026-09-06 21:19 ` Patchtest results for " patchtest
2026-09-06 21:02 ` AdrianF [this message]
2026-09-06 21:02 ` [PATCH 4/9] oe-selftest: tinfoil: test prepared task runner AdrianF
2026-09-06 21:02 ` [PATCH 5/9] devtool: ide-sdk: run do_install through BitBake AdrianF
2026-09-06 21:02 ` [PATCH 6/9] oe-selftest: devtool ide-sdk: test install task AdrianF
2026-09-06 21:02 ` [PATCH 7/9] runqemu-export-rootfs: set PSEUDO_INCLUDE_PATHS for unfsd AdrianF
2026-09-06 21:02 ` [PATCH 8/9] devtool: deploy: make pseudo calls independent of bitbake.conf AdrianF
2026-09-06 21:02 ` [PATCH 9/9] devtool: deploy: remove dead files_list computation AdrianF
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=20260906210307.2793974-4-adrian.freihofer@siemens.com \
--to=adrian.freihofer@siemens.com \
--cc=openembedded-core@lists.openembedded.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