From: Tom Tromey <tromey@redhat.com>
To: Project Archer <archer@sourceware.org>
Subject: [python] fix typo in command.py
Date: Wed, 01 Jul 2009 15:55:00 -0000 [thread overview]
Message-ID: <m3y6r82yba.fsf@fleche.redhat.com> (raw)
Taras pointed out that command.py was missing a paren.
Tom
diff --git a/gdb/python/lib/gdb/command/backtrace.py b/gdb/python/lib/gdb/command/backtrace.py
index 689b94b..c49fd55 100644
--- a/gdb/python/lib/gdb/command/backtrace.py
+++ b/gdb/python/lib/gdb/command/backtrace.py
@@ -174,7 +174,7 @@ Use of the 'raw' qualifier avoids any filtering by loadable modules.
# However, should still number as if starting from newest
newest_frame = gdb.selected_thread ().newest_frame ()
iter = itertools.imap (FrameWrapper,
- FrameIterator (newest_frame)
+ FrameIterator (newest_frame))
if filter:
iter = gdb.backtrace.create_frame_filter (iter)
reply other threads:[~2009-07-01 15:55 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=m3y6r82yba.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@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).