public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Bruno Larsen <blarsen@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/testsuite: Fix formatting of python script Date: Tue, 11 Oct 2022 09:41:24 +0000 (GMT) [thread overview] Message-ID: <20221011094124.A21A33858290@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=73fa80feee65dde8cbbdacca1b76b4f3f6af62cb commit 73fa80feee65dde8cbbdacca1b76b4f3f6af62cb Author: Bruno Larsen <blarsen@redhat.com> Date: Tue Oct 11 11:22:37 2022 +0200 gdb/testsuite: Fix formatting of python script The python black formatter was complaining about formatting on the script gdb.python/pretty-print-call-by-hand.py. This commit changed the offending lines to make the formatter happy. Diff: --- gdb/testsuite/gdb.python/pretty-print-call-by-hand.py | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/gdb/testsuite/gdb.python/pretty-print-call-by-hand.py b/gdb/testsuite/gdb.python/pretty-print-call-by-hand.py index f8f5df678f8..5343af831a7 100644 --- a/gdb/testsuite/gdb.python/pretty-print-call-by-hand.py +++ b/gdb/testsuite/gdb.python/pretty-print-call-by-hand.py @@ -21,21 +21,25 @@ class MytypePrinter: self.val = val def to_string(self): - calls = gdb.parse_and_eval('f()') - return "mytype is %s" % self.val['x'] + calls = gdb.parse_and_eval("f()") + return "mytype is %s" % self.val["x"] + def ec_lookup_function(val): typ = val.type if typ.code == gdb.TYPE_CODE_REF: typ = typ.target() - if str(typ) == 'struct mytype': + if str(typ) == "struct mytype": return MytypePrinter(val) return None + def disable_lookup_function(): ec_lookup_function.enabled = False + def enable_lookup_function(): ec_lookup_function.enabled = True + gdb.pretty_printers.append(ec_lookup_function)
reply other threads:[~2022-10-11 9:41 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221011094124.A21A33858290@sourceware.org \ --to=blarsen@sourceware.org \ --cc=gdb-cvs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).