From: Kieran Bingham <kieran.bingham@linaro.org>
To: jan.kiszka@siemens.com, linux-kernel@vger.kernel.org
Cc: lee.jones@linaro.org, peter.griffin@linaro.org,
maxime.coquelin@st.com,
Kieran Bingham <kieran.bingham@linaro.org>
Subject: [PATCH 4/8] scripts/gdb: Provide exception catching parser
Date: Mon, 22 Feb 2016 15:24:08 +0000 [thread overview]
Message-ID: <1456154652-29023-5-git-send-email-kieran.bingham@linaro.org> (raw)
In-Reply-To: <1456154652-29023-1-git-send-email-kieran.bingham@linaro.org>
If we attempt to read a value that is not available to GDB, an exception
is raised. Most of the time, this is a good thing; however on occasion
we will want to be able to determine if a symbol is available.
By catching the exception to simply return None, we can determine if we
tried to read an invalid value, without the exception taking our execution
context away from us
Signed-off-by: Kieran Bingham <kieran.bingham@linaro.org>
---
scripts/gdb/linux/utils.py | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/scripts/gdb/linux/utils.py b/scripts/gdb/linux/utils.py
index 0893b326a28b..dbe2ad78048c 100644
--- a/scripts/gdb/linux/utils.py
+++ b/scripts/gdb/linux/utils.py
@@ -154,3 +154,10 @@ def get_gdbserver_type():
if gdbserver_type is not None and hasattr(gdb, 'events'):
gdb.events.exited.connect(exit_handler)
return gdbserver_type
+
+
+def gdb_eval_or_none(expresssion):
+ try:
+ return gdb.parse_and_eval(expresssion)
+ except:
+ return None
--
2.5.0
next prev parent reply other threads:[~2016-02-22 15:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 15:24 [PATCHv2 0/8] gdb/scripts: Linux awareness debug commands Kieran Bingham
2016-02-22 15:24 ` [PATCH 1/8] scripts/gdb: Provide linux constants Kieran Bingham
2016-02-22 15:24 ` [PATCH 2/8] scripts/gdb: Provide a kernel list item generators Kieran Bingham
2016-02-22 15:24 ` [PATCH 3/8] scripts/gdb: Convert modules usage to lists functions Kieran Bingham
2016-02-22 15:24 ` Kieran Bingham [this message]
2016-02-22 15:24 ` [PATCH 5/8] scripts/gdb: Support !CONFIG_MODULES gracefully Kieran Bingham
2016-02-22 15:24 ` [PATCH 6/8] scripts/gdb: Add io resource readers Kieran Bingham
2016-02-22 15:24 ` [PATCH 7/8] scripts/gdb: Add mount point list command Kieran Bingham
2016-02-22 15:24 ` [PATCH 8/8] scripts/gdb: Add meminfo command Kieran Bingham
2016-02-24 9:44 ` Kieran Bingham
2016-02-29 16:36 ` [PATCHv2 0/8] gdb/scripts: Linux awareness debug commands Jan Kiszka
2016-02-29 17:01 ` Kieran Bingham
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=1456154652-29023-5-git-send-email-kieran.bingham@linaro.org \
--to=kieran.bingham@linaro.org \
--cc=jan.kiszka@siemens.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.coquelin@st.com \
--cc=peter.griffin@linaro.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
all inboxes | Powered by JetHome®