Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "adrian.freihofer@gmail.com" <adrian.freihofer@gmail.com>
To: enguerrand.de-ribaucourt@savoirfairelinux.com,
	 openembedded-core@lists.openembedded.org
Cc: Adrian Freihofer <adrian.freihofer@siemens.com>
Subject: Re: [OE-core] [PATCH 12/20] devtool: ide-sdk: enforce LLDB for Cargo
Date: Thu, 29 Oct 2026 00:08:23 +0100	[thread overview]
Message-ID: <8ab23bcff84d5834ceef6fe5e5d0a30411036a82.camel@gmail.com> (raw)
In-Reply-To: <20261026-devtool-ide-sdk-cargo-v1-12-d4504e124d07@savoirfairelinux.com>

Hi,

This is a blocking issue. uses_lldb is wired into ide_sdk.py (debugger
selection, wants_lldb_server) and ide_code.py, but not into
ide_plugins/ide_none.py. ide_none.setup_modified_recipe() still checks
toolchain == 'clang'.

With --ide=none or --ide=all on a Cargo recipe, the image gets lldb-
server and RecipeLldbNative, but GdbCrossConfigNone generates gdbserver
scripts for a gdbserver that isn't on the target. Please use
modified_recipe.uses_lldb there.

No test can catch this today, since all Cargo tests use --ide=code
only. Please add a Cargo --ide=code --ide=none test without QEMU,
asserting the generated debugger configuration and install script, as
the C++ _test_code_and_none_qemu does.

Also, the comment citing the VS Code Rust docs is good. Please add one
sentence on why cppdbg/GDB can't resolve Rust breakpoints.

Best regards
Adrian

  reply	other threads:[~2026-10-28 23:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  8:55 [PATCH 00/20] devtool: ide-sdk: add support for Rust recipes Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 01/20] cargo-example: add minimal selftest fixture Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 02/20] devtool: ide-sdk: capture Cargo cross environment Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 03/20] devtool: ide-sdk: export recipe Cargo configuration Enguerrand de Ribaucourt
2026-10-28 22:40   ` [OE-core] " adrian.freihofer
2026-10-26  8:55 ` [PATCH 04/20] devtool: ide-sdk: recommend Rust Analyzer for Cargo Enguerrand de Ribaucourt
2026-10-28 22:48   ` [OE-core] " adrian.freihofer
2026-10-26  8:55 ` [PATCH 05/20] devtool: ide-sdk: configure " Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 06/20] devtool: ide-sdk: share IntelliSense architecture mapping Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 07/20] devtool: ide-sdk: configure Cargo C++ IntelliSense Enguerrand de Ribaucourt
2026-10-28 22:59   ` [OE-core] " adrian.freihofer
2026-10-26  8:55 ` [PATCH 08/20] devtool: ide-sdk: generalize binary install task name Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 09/20] devtool: ide-sdk: extract install task definition Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 10/20] devtool: ide-sdk: order install after optional build task Enguerrand de Ribaucourt
2026-10-28 23:01   ` [OE-core] " adrian.freihofer
2026-10-26  8:55 ` [PATCH 11/20] devtool: ide-sdk: add Cargo " Enguerrand de Ribaucourt
2026-10-28 23:04   ` [OE-core] " adrian.freihofer
2026-10-26  8:55 ` [PATCH 12/20] devtool: ide-sdk: enforce LLDB for Cargo Enguerrand de Ribaucourt
2026-10-28 23:08   ` adrian.freihofer [this message]
2026-10-26  8:55 ` [PATCH 13/20] devtool: ide-sdk: parse Rust debug path remaps Enguerrand de Ribaucourt
2026-10-28 23:16   ` [OE-core] " adrian.freihofer
2026-10-26  8:55 ` [PATCH 14/20] devtool: ide-sdk: remap Cargo sources for BitBake builds Enguerrand de Ribaucourt
2026-10-28 23:28   ` [OE-core] " adrian.freihofer
2026-10-26  8:55 ` [PATCH 15/20] devtool: ide-sdk: map Cargo workspace sources for LLDB Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 16/20] devtool: ide-sdk: map libstd-rs sources to Rust SDK Enguerrand de Ribaucourt
2026-10-28 23:23   ` [OE-core] " adrian.freihofer
2026-10-26  8:55 ` [PATCH 17/20] oeqa/selftest: share source breakpoint lookup Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 18/20] oeqa/selftest: run IDE tasks with configured environment Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 19/20] oeqa/selftest: debug Cargo example over QEMU slirp Enguerrand de Ribaucourt
2026-10-26  8:55 ` [PATCH 20/20] oeqa/selftest: verify Cargo rebuild and redeploy Enguerrand de Ribaucourt
2026-10-28 23:30 ` [OE-core] [PATCH 00/20] devtool: ide-sdk: add support for Rust recipes 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=8ab23bcff84d5834ceef6fe5e5d0a30411036a82.camel@gmail.com \
    --to=adrian.freihofer@gmail.com \
    --cc=adrian.freihofer@siemens.com \
    --cc=enguerrand.de-ribaucourt@savoirfairelinux.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