public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@efficios.com>
Subject: [pushed] gdb: re-format Python code with black 23
Date: Tue, 18 Apr 2023 12:27:22 -0400	[thread overview]
Message-ID: <20230418162722.69512-1-simon.marchi@efficios.com> (raw)

Change-Id: I849d10d69c254342bf01e955ffe62a2b60f9de4b
---
 gdb/gdbarch_components.py             | 7 +++++--
 gdb/testsuite/gdb.python/py-unwind.py | 1 +
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/gdb/gdbarch_components.py b/gdb/gdbarch_components.py
index a0e35b8b5e81..62cd430cbae0 100644
--- a/gdb/gdbarch_components.py
+++ b/gdb/gdbarch_components.py
@@ -918,8 +918,11 @@ Return true if the typedef record needs to be replaced.".
 Return 0 by default""",
     type="bool",
     name="dwarf2_omit_typedef_p",
-    params=[("struct type *", "target_type"), ("const char *", "producer"),
-            ("const char *", "name")],
+    params=[
+        ("struct type *", "target_type"),
+        ("const char *", "producer"),
+        ("const char *", "name"),
+    ],
     predefault="default_dwarf2_omit_typedef_p",
     invalid=False,
 )
diff --git a/gdb/testsuite/gdb.python/py-unwind.py b/gdb/testsuite/gdb.python/py-unwind.py
index 201b629f9fe8..8e24a3190c7b 100644
--- a/gdb/testsuite/gdb.python/py-unwind.py
+++ b/gdb/testsuite/gdb.python/py-unwind.py
@@ -198,6 +198,7 @@ def capture_frame_information(frame):
 # capture_all_frame_information.
 all_frame_information = []
 
+
 # Fill in the global ALL_FRAME_INFORMATION list.
 def capture_all_frame_information():
     global all_frame_information
-- 
2.40.0


                 reply	other threads:[~2023-04-18 16:27 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=20230418162722.69512-1-simon.marchi@efficios.com \
    --to=simon.marchi@efficios.com \
    --cc=gdb-patches@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).