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 13/14] oe-selftest: devtool: add test for gdb pretty-printing
Date: Fri, 02 Jan 2026 15:44:01 +0100 [thread overview]
Message-ID: <DFE6MBAAWOB4.26A0XX5Y79R3F@bootlin.com> (raw)
In-Reply-To: <20251231114718.4031606-14-adrian.freihofer@siemens.com>
On Wed Dec 31, 2025 at 12:46 PM CET, Adrian Freihofer via lists.openembedded.org wrote:
> From: Adrian Freihofer <adrian.freihofer@siemens.com>
>
> This extends the existing devtool IDE SDK tests to verify that gdb
> pretty-printing is working correctly.
>
> Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com>
> ---
Hi Adrian,
Thanks for the new version, but it looks like it is still failing:
2026-01-02 10:09:04,822 - oe-selftest - INFO - 11: 2/36 112/655 (365.52s) (0 failed) (devtool.DevtoolIdeSdkTests.test_devtool_ide_sdk_code_cmake)
2026-01-02 10:09:04,822 - 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 3237, in test_devtool_ide_sdk_code_cmake
self._verify_launch_json_debugging(tempdir, qemu, recipe_name, example_exe)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/devtool.py", line 3106, in _verify_launch_json_debugging
self._verify_launch_config(tempdir, config, tasks, qemu, example_exe,
~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
self._gdb_debug_cpp_example, self._gdb_debug_cpp_example_check)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/devtool.py", line 3206, in _verify_launch_config
debug_check_func(r.output, DevtoolIdeSdkTests.MAGIC_STRING_ORIG)
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/devtool.py", line 2750, in _gdb_debug_cpp_example_check
self.assertRegex(gdb_output, r"\$\d+ = std::vector of length 3, capacity 3 = \{1, 2, 3\}")
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.13/unittest/case.py", line 1369, in assertRegex
raise self.failureException(msg)
AssertionError: Regex didn't match: '\\$\\d+ = std::vector of length 3, capacity 3 = \\{1, 2, 3\\}' not found in '_start () at ../sysdeps/aarch64/dl-start.S:23\n23\tENTRY (_start)\nBreakpoint 1 at 0xaaaaaaaa1400: file /usr/src/debug/cmake-example/1.0/cpp-example.cpp, line 15.\n\nBreakpoint 1, main (argc=1, argv=0xfffffffffd08) at /usr/src/debug/cmake-example/1.0/cpp-example.cpp:15\n15\t{\nBreakpoint 2 at 0xfffff7f91d70: file /usr/src/debug/cmake-example/1.0/cpp-example-lib.cpp, line 28.\n\nBreakpoint 2, CppExample::print_json (this=0xfffffffffac8) at /usr/src/debug/cmake-example/1.0/cpp-example-lib.cpp:28\n28\t jobj = json_object_new_object();\n$1 = 0\n$2 = -3\n14\t inline static const std::string test_string = "cpp-example-lib Magic: 123456789";\n55\t std::vector<int> numbers = {1, 2, 3};\nBreakpoint 3 at 0xaaaaaaaa1780: file /usr/src/debug/cmake-example/1.0/cpp-example.cpp, line 56.\n\nBreakpoint 3, std::uninitialized_copy<int const*, int*> (__first=<optimized out>, __last=<optimized out>, __result=<optimized out>) at /usr/src/debug/cmake-example/1.0/cpp-example.cpp:56\n56\t std::cout << "Traversing std::vector<int> numbers:" << std::endl;\nAttempt to use a type name as an expression\n[Inferior 1 (process 346) exited normally]'
And a similar one for devtool.DevtoolIdeSdkTests.test_devtool_ide_sdk_none_qemu.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/3078
I know debugging this might be a bit tough, as it is arm host only. If
you have doubts about what is failing, I can do some tests next week.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-02 14:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 11:46 [PATCH v2 00/14] IDE SDK Improvements AdrianF
2025-12-31 11:46 ` [PATCH v2 01/14] devtool: ide-sdk find bitbake-setup init-build-env AdrianF
2025-12-31 11:46 ` [PATCH v2 02/14] oe-selftest: devtool: DevtoolIdeSdkTests debug logging AdrianF
2025-12-31 11:46 ` [PATCH v2 03/14] cpp-example: run as a service AdrianF
2025-12-31 11:46 ` [PATCH v2 04/14] oe-selftest: devtool: check example services are running AdrianF
2025-12-31 11:46 ` [PATCH v2 05/14] devtool: ide-sdk: add gdbserver attach mode support AdrianF
2025-12-31 11:46 ` [PATCH v2 06/14] devtool: ide-sdk: move code to ide_none AdrianF
2025-12-31 11:46 ` [PATCH v2 07/14] devtool: ide-sdk: make install_and_deploy script pass target arg AdrianF
2025-12-31 11:46 ` [PATCH v2 08/14] devtool: ide-sdk: vscode replace scripts AdrianF
2025-12-31 11:46 ` [PATCH v2 09/14] oe-selftest: devtool ide-sdk cover vscode remote debugging AdrianF
2025-12-31 11:46 ` [PATCH v2 10/14] devtool: ide-sdk: evaluate DEBUG_PREFIX_MAP AdrianF
2025-12-31 11:46 ` [PATCH v2 11/14] cpp-example: Add std::vector example AdrianF
2025-12-31 11:46 ` [PATCH v2 12/14] devtool: ide-sdk: Support GDB pretty-printing for C++ STL types AdrianF
2025-12-31 11:46 ` [PATCH v2 13/14] oe-selftest: devtool: add test for gdb pretty-printing AdrianF
2026-01-02 14:44 ` Mathieu Dubois-Briand [this message]
2025-12-31 11:46 ` [PATCH v2 14/14] oe-selftest: devtool: add compile step in ide-sdk tests AdrianF
2026-01-13 8:17 ` [OE-core] [PATCH v2 00/14] IDE SDK Improvements Antonin Godard
2026-01-14 18:37 ` adrian.freihofer
2026-01-20 11:59 ` Antonin Godard
2026-01-26 7:47 ` adrian.freihofer
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=DFE6MBAAWOB4.26A0XX5Y79R3F@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