public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/65366] New: gdbhooks.py is incompatible with Python3 Date: Mon, 09 Mar 2015 21:39:00 -0000 [thread overview] Message-ID: <bug-65366-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65366 Bug ID: 65366 Summary: gdbhooks.py is incompatible with Python3 Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: jan.kratochvil at redhat dot com Host: x86_64-linux-gnu GDB Python support upstream has always been compatible with Python3. Fedora since F-22 builds GDB with Python3 by default (<=F-21 GDB used Python2). gdbhooks.py in GCC trunk is compatible with Python2 but not Python3. gdb-7.9-10.fc23.x86_64 (gdb) source /home/jkratoch/redhat/gcchead/gcc/c/../gdbhooks.py File "/home/jkratoch/redhat/gcchead/gcc/c/../gdbhooks.py", line 372 print format_[i] ^ SyntaxError: Missing parentheses in call to 'print' Additionally after fixing the 'print' incompatibility one gets randomly: dependence_info = {clique = 257, Python Exception <class 'NameError'> name 'long' is not defined: base = 1}}}, type = }, I have a patch, going to post it.
next reply other threads:[~2015-03-09 21:39 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-09 21:39 jan.kratochvil at redhat dot com [this message] 2015-03-10 14:20 ` [Bug other/65366] " jan.kratochvil at redhat dot com 2015-06-02 7:37 ` jkratoch at gcc dot gnu.org 2015-06-02 7:40 ` jan.kratochvil at redhat dot com 2015-06-03 8:28 ` rguenth at gcc dot gnu.org 2015-06-08 13:36 ` jkratoch at gcc dot gnu.org 2015-06-08 13:38 ` jan.kratochvil at redhat dot com
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=bug-65366-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).