public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: wzh@ilbers.de, jan.kiszka@siemens.com
Subject: Re: [PATCH v2 2/2] bitbake: Remove custom exception backtrace formatting
Date: Tue, 10 Mar 2026 13:21:22 +0200	[thread overview]
Message-ID: <4bbee255-b69b-42e5-91f4-c85642e9e56e@ilbers.de> (raw)
In-Reply-To: <20260306161548.1102004-3-felix.moessbauer@siemens.com>

Hello Felix,

Would you like to resend the patchset with restored authors or I can do 
that?

06.03.2026 18:15, 'Felix Moessbauer' via isar-users wrote:
> Backport of upstream bitbake patch c25e7ed128b9fd5b53d28d678238e2f3af52ef8b.
>
> Removes the code in bitbake to show custom backtrace formatting for
> exceptions. In particular, the bitbake exception code prints function
> arguments, which while helpful is a security problem when passwords and
> other secrets can be passed as function arguments.
>
> As it turns out, the handling of the custom serialized exception stack
> frames was pretty much made obsolete by d7db75020ed ("event/msg: Pass
> formatted exceptions"), which changed the events to pass a preformatted
> stacktrack list of strings, but the passing of the serialized data was
> never removed.
>
> Change all the code to use the python traceback API to format exceptions
> instead of the custom code; conveniently traceback.format_exception()
> also returns a list of stack trace strings, so it can be used as a drop
> in replacement for bb.exception.format_exception()
>
> [Felix: adjusted to bitbake path in isar repo]
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/4bbee255-b69b-42e5-91f4-c85642e9e56e%40ilbers.de.

  parent reply	other threads:[~2026-03-10 11:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06 16:15 [PATCH v2 0/2] bitbake: Update to 2.8.1 release (no update!) 'Felix Moessbauer' via isar-users
2026-03-06 16:15 ` [PATCH v2 1/2] partial revert of "Bitbake: use LAYERDIR_RE when setting BBFILE_PATTERN_x" 'Felix Moessbauer' via isar-users
2026-03-06 16:15 ` [PATCH v2 2/2] bitbake: Remove custom exception backtrace formatting 'Felix Moessbauer' via isar-users
2026-03-06 16:40   ` 'Jan Kiszka' via isar-users
2026-03-10 11:21   ` Anton Mikanovich [this message]
2026-03-09  9:56 ` [PATCH v2 0/2] bitbake: Update to 2.8.1 release (no update!) Zhihang Wei
2026-03-09 11:07   ` 'MOESSBAUER, Felix' via isar-users
2026-03-09 12:37     ` 'Jan Kiszka' via isar-users

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=4bbee255-b69b-42e5-91f4-c85642e9e56e@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=wzh@ilbers.de \
    /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