public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <adrian.freihofer@siemens.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 9/9] oe-selftest: devtool ide-sdk: add clang/LLDB test
Date: Tue, 24 Mar 2026 18:22:34 +0100	[thread overview]
Message-ID: <DHB6PUB4HG73.2D0X4F8KV6N7K@bootlin.com> (raw)
In-Reply-To: <20260322151320.661246-10-adrian.freihofer@siemens.com>

On Sun Mar 22, 2026 at 4:13 PM CET, Adrian Freihofer via lists.openembedded.org wrote:
> From: Adrian Freihofer <adrian.freihofer@siemens.com>
>
> Add test_devtool_ide_sdk_code_cmake_clang to verify the full devtool
> ide-sdk workflow for a cmake recipe built with clang.  Unlike the gcc
> variant the clang recipe uses lldb-server for remote debugging and
> CodeLLDB (vadimcn.vscode-lldb) as the VS Code debug adapter.
>
> The test covers:
> - devtool modify + devtool ide-sdk with ide=code
> - cmake preset compilation and CTest execution (same as the gcc test)
> - extensions.json recommends vadimcn.vscode-lldb
> - launch.json uses "type": "lldb" (CodeLLDB) instead of "type": "cppdbg"
> - End-to-end lldb --batch remote debugging session via lldb-server
>   platform mode running on qemu
>
> Supporting changes:
> - _write_bb_config: accept optional extra_packages parameter so the
>   clang test can add lldb-server to IMAGE_INSTALL
> - _verify_launch_json_lldb: new helper that validates the CodeLLDB
>   launch.json structure (type, initCommands, program, cwd, preLaunchTask)
> - _lldb_server_debugging_once: new helper that reads the preLaunchTask
>   SSH command from tasks.json, starts lldb-server on the target, and
>   runs lldb --batch to verify a breakpoint at main is hit
> - _verify_service_running: use pgrep with exact regex (^name$) for exact
>   process name matching; without that, pgrep would also match
>   cmake-example-clang (truncated to 'cmake-example-c' in
>   /proc/pid/comm) when checking for cmake-example, returning two PIDs
>   and failing the isdigit() assertion
>
> Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
> ---

Hi Adrian,

Thanks for your patch.

I believe the added test is failing on the autobuilder:

2026-03-24 13:25:52,674 - oe-selftest - INFO - devtool.DevtoolIdeSdkTests.test_devtool_ide_sdk_code_cmake_clang (subunit.RemotedTestCase)
2026-03-24 13:25:52,674 - oe-selftest - INFO -  ... FAIL
...
2026-03-24 15:55:22,676 - oe-selftest - INFO - FAIL: devtool.DevtoolIdeSdkTests.test_devtool_ide_sdk_code_cmake_clang (subunit.RemotedTestCase)
2026-03-24 15:55:22,676 - oe-selftest - INFO - ----------------------------------------------------------------------
2026-03-24 15:55:22,676 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/devtool.py", line 3864, in test_devtool_ide_sdk_code_cmake_clang
    self._lldb_server_debugging_once(tempdir, qemu, recipe_name,
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                                     DevtoolIdeSdkTests.MAGIC_STRING_ORIG)
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/devtool.py", line 3805, in _lldb_server_debugging_once
    r = runCmd(lldb_batch, output_log=self._cmd_logger)
  File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/utils/commands.py", line 214, in runCmd
    raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, exc_output))
...
(lldb) b main
Breakpoint 1: where = cmake-example-clang`main + 48 at cpp-example.cpp:19:5, address = 0x0000000000001750
(lldb) run
/tmp/lldb_server_1234_usr-bin-cmake-example-clang_multi/cmake-example-clang: error while loading shared libraries: libcmake-example-clang-lib.so.1: cannot open shared object file: No such file or directory
Process 335 launched: '/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-2935310/tmp/work/cortexa57-poky-linux/cmake-example-clang/1.0/image/usr/bin/cmake-example-clang' (aarch64)
Process 335 exited with status = 127 (0x0000007f)
(lldb) continue
error: Process must be launched.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3606
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3389

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



      reply	other threads:[~2026-03-24 17:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-22 15:12 [PATCH v2 0/9] devtool: ide-sdk clang/LLDB support and minor fixes AdrianF
2026-03-22 15:12 ` [PATCH v2 1/9] oe-selftest: devtool: use stat for reading user/group names in ide-sdk tests AdrianF
2026-03-22 15:12 ` [PATCH v2 2/9] oe-selftest: devtool: GDB breakpoint after std::vector is constructed AdrianF
2026-03-22 15:12 ` [PATCH v2 3/9] oe-selftest: devtool: use assertRegex to match test output for meson AdrianF
2026-03-22 15:12 ` [PATCH v2 4/9] oe-selftest/cpp-example: fix conf file ownership with static UIDs/GIDs AdrianF
2026-03-22 15:12 ` [PATCH v2 5/9] devtool: ide-sdk: use TOOLCHAIN not TCOVERRIDE AdrianF
2026-03-22 15:12 ` [PATCH v2 6/9] devtool: ide-sdk debugger back-end abstraction AdrianF
2026-03-22 15:12 ` [PATCH v2 7/9] devtool: ide-sdk add LLDB support for clang toolchain AdrianF
2026-03-22 15:12 ` [PATCH v2 8/9] meta-selftest: refactor cpp examples into .inc files and add clang variants AdrianF
2026-03-22 15:13 ` [PATCH v2 9/9] oe-selftest: devtool ide-sdk: add clang/LLDB test AdrianF
2026-03-24 17:22   ` Mathieu Dubois-Briand [this message]

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=DHB6PUB4HG73.2D0X4F8KV6N7K@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=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