From: Michael Tretter <m.tretter@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Bruno Knittel <bruno.knittel@bruker.com>,
Michael Tretter <m.tretter@pengutronix.de>
Subject: [PATCH] scripts: gdb: fix missing pbl_barebox_break error message
Date: Mon, 17 Aug 2026 16:13:26 +0200 [thread overview]
Message-ID: <20260817-fix-gdb-script-error-message-v1-1-4ebbaff5c131@pengutronix.de> (raw)
From: Bruno Knittel <bruno.knittel@bruker.com>
If no pbl_barebox_break symbol is found in the file provided to
bb-load-symbols, the script is failing with a Python exception stating
that BBSymbols has no path attribute.
Fix the error handling to actually print the error message.
Signed-off-by: Bruno Knittel <bruno.knittel@bruker.com>
Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
---
scripts/gdb/helper.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/gdb/helper.py b/scripts/gdb/helper.py
index 40417898902e..e92b1fe65a57 100644
--- a/scripts/gdb/helper.py
+++ b/scripts/gdb/helper.py
@@ -33,7 +33,7 @@ class BBSymbols(gdb.Command):
symbol = section.get_symbol_by_name("pbl_barebox_break")
if not symbol:
gdb.write("Symbol pbl_barebox_break in section {} in file {} not found\n"
- .format(section.name, self.path), gdb.STDERR)
+ .format(section.name, path), gdb.STDERR)
return
symbol = symbol[0]
pc = gdb.parse_and_eval("$pc")
---
base-commit: 3317ac1baff3b0226caba7f83f3da61bc407343a
change-id: 20260817-fix-gdb-script-error-message-2b213a0644c3
Best regards,
--
Michael Tretter <m.tretter@pengutronix.de>
next reply other threads:[~2026-08-17 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 14:13 Michael Tretter [this message]
2026-08-19 7:04 ` Sascha Hauer
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=20260817-fix-gdb-script-error-message-v1-1-4ebbaff5c131@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=bruno.knittel@bruker.com \
--cc=s.hauer@pengutronix.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