From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [rfc patch+7.11] gdb-gdb.py: SyntaxError: Missing parentheses in call to 'print'
Date: Mon, 22 Feb 2016 15:56:00 -0000 [thread overview]
Message-ID: <20160222155646.GA1869@host1.jankratochvil.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Hi,
after build GDB
--with-python=/usr/bin/python3
and for example stripping ./gdb and running:
./gdb -data-directory data-directory/ -iex "add-auto-load-safe-path $PWD/gdb-gdb.gdb" -iex "add-auto-load-safe-path $PWD/gdb-gdb.py" ./gdb
I get:
Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
File "/home/jkratoch/redhat/gdb-test-python3/gdb/gdb-gdb.py", line 91
print "Warning: Cannot find enum type_flag_value type."
^
SyntaxError: Missing parentheses in call to 'print'
(top-gdb) q
The fix would be obvious:
s/print \(".*"\)/print (\1)
But then I was curious I do not see the warning messsage anyway.
So I tried to append \n to that string but I still do not see the warning.
But I do not know why. This patch is probably right and it could be checked
in as "obvious" but given the warning still is not seen who knows.
Jan
[-- Attachment #2: 1 --]
[-- Type: text/plain, Size: 1261 bytes --]
gdb/ChangeLog
2016-02-22 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb-gdb.py (class TypeFlagsPrinter): Use parentheses for print.
diff --git a/gdb/gdb-gdb.py b/gdb/gdb-gdb.py
index 4f3ac1c..9a12baf 100644
--- a/gdb/gdb-gdb.py
+++ b/gdb/gdb-gdb.py
@@ -88,14 +88,14 @@ class TypeFlagsPrinter:
try:
flags = gdb.lookup_type("enum type_flag_value")
except:
- print "Warning: Cannot find enum type_flag_value type."
- print " `struct type' pretty-printer will be degraded"
+ print("Warning: Cannot find enum type_flag_value type.")
+ print(" `struct type' pretty-printer will be degraded")
return
try:
iflags = gdb.lookup_type("enum type_instance_flag_value")
except:
- print "Warning: Cannot find enum type_instance_flag_value type."
- print " `struct type' pretty-printer will be degraded"
+ print("Warning: Cannot find enum type_instance_flag_value type.")
+ print(" `struct type' pretty-printer will be degraded")
return
# Note: TYPE_FLAG_MIN is a duplicate of TYPE_FLAG_UNSIGNED,
# so exclude it from the list we are building.
next reply other threads:[~2016-02-22 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 15:56 Jan Kratochvil [this message]
2016-02-22 16:12 ` Simon Marchi
2016-02-22 16:20 ` [commit] " Jan Kratochvil
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=20160222155646.GA1869@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.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