From: Eli Zaretskii <eliz@gnu.org>
To: elpa@tromey.com
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: add ability to "source" Python code
Date: Sun, 08 Feb 2009 04:08:00 -0000 [thread overview]
Message-ID: <uy6whsh8u.fsf@gnu.org> (raw)
In-Reply-To: <m3hc3520f9.fsf@fleche.redhat.com>
> From: Tom Tromey <elpa@tromey.com>
> Date: Sat, 07 Feb 2009 18:16:10 -0700
>
> This patch adds Python support to the gdb "source" command.
> I added this after several user questions about how to do this.
> Also, due to completion, it is much more convenient than the
> equivalent "python" command.
Thanks.
> This could use a documentation review.
The documentation part is okay, except that I'd add a @cindex entry
there about sourcing Python code files.
However, I don't think I like the idea of GDB barfing if Python
support is not compiled in. I think it should simply try to interpret
the file as GDB scripting commands.
I also think we need a NEWS entry for this feature.
next prev parent reply other threads:[~2009-02-08 4:08 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 1:16 Tom Tromey
2009-02-08 1:34 ` Tom Tromey
2009-02-08 4:10 ` Eli Zaretskii
2009-02-08 4:08 ` Eli Zaretskii [this message]
2009-02-09 1:53 ` Doug Evans
2009-02-09 4:09 ` Eli Zaretskii
2009-02-10 1:37 ` Tom Tromey
2009-02-10 1:30 ` Tom Tromey
2009-02-09 1:35 ` Doug Evans
2009-02-10 0:00 ` Pedro Alves
2009-02-10 1:29 ` Tom Tromey
2009-02-10 2:36 ` Pedro Alves
2009-02-10 3:48 ` Daniel Jacobowitz
2009-02-10 9:34 ` Eli Zaretskii
2009-02-10 11:58 ` Thiago Jung Bauermann
2009-02-10 17:04 ` Tom Tromey
2009-02-11 2:25 ` Paul Pluzhnikov
2009-02-11 6:09 ` Joel Brobecker
2009-02-11 19:51 ` Tom Tromey
2009-02-11 20:21 ` Eli Zaretskii
2009-02-11 20:39 ` Joel Brobecker
2009-02-11 21:06 ` Eli Zaretskii
2009-02-11 21:26 ` Matt Rice
2009-02-11 21:49 ` Eli Zaretskii
2009-02-11 21:55 ` Eli Zaretskii
2009-02-11 22:01 ` Joel Brobecker
2009-02-12 3:59 ` Eli Zaretskii
2009-02-12 6:27 ` Joel Brobecker
2009-02-12 20:32 ` Thiago Jung Bauermann
2009-02-12 22:38 ` Eli Zaretskii
2009-02-13 8:42 ` Joel Brobecker
2009-02-13 15:23 ` Eli Zaretskii
2009-02-17 0:58 ` Joel Brobecker
2009-02-17 5:54 ` Eli Zaretskii
2009-02-17 20:37 ` Tom Tromey
2009-02-19 21:45 ` Joel Brobecker
2009-06-01 3:57 ` Thiago Jung Bauermann
2009-06-01 5:05 ` Paul Pluzhnikov
2009-06-01 15:33 ` Eli Zaretskii
2009-06-01 15:46 ` Eli Zaretskii
2009-06-01 17:54 ` Thiago Jung Bauermann
2009-06-10 23:10 ` Tom Tromey
2009-06-11 14:19 ` Joel Brobecker
2009-07-03 7:21 ` Paul Pluzhnikov
2010-01-15 7:21 ` Joel Brobecker
2010-01-15 9:13 ` Joel Brobecker
2010-01-15 18:03 ` Tom Tromey
2010-01-18 6:33 ` Joel Brobecker
2010-01-18 17:48 ` Eli Zaretskii
2010-01-19 10:32 ` Joel Brobecker
2009-02-11 20:43 ` Daniel Jacobowitz
2009-02-11 21:08 ` Eli Zaretskii
2009-02-11 21:16 ` Daniel Jacobowitz
2009-02-11 21:46 ` Eli Zaretskii
2009-02-11 20:54 ` Tom Tromey
2009-02-11 21:11 ` Eli Zaretskii
2009-02-11 20:46 ` Joel Brobecker
2009-02-11 20:58 ` Tom Tromey
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=uy6whsh8u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=elpa@tromey.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