From: Phil Muldoon <pmuldoon@redhat.com>
To: archer@sourceware.org
Subject: archer/tromey patches left to merge
Date: Mon, 14 Oct 2013 11:26:00 -0000 [thread overview]
Message-ID: <525BD4EA.60907@redhat.com> (raw)
Currently we still have some patches in the archer tromey/python
branch. I want to finally close this branch, so I decided to write an
email about what is left, and try to decide what we should do about
those patches. Here is what we have left:
* The -P, --python command line switch
This feature changes interpretation of the command line so that the
argument immediately following this switch is taken to be the name
of a Python script file. This option stops option processing;
subsequent options are passed to Python as sys.argv.
* gdb.cli() command.
This invokes a GDB command-line from a Python script. Usage of this
command (AFAIK) is exclusively with the -P switch. (You cannot run
this command from the gdb command line -- it generates an error
about recursive instantiatiations.)
I understand why this exists (to invoke an interactive GDB
command-line from a Python script), but I feel a little dubious
about it. Can we can construct a solid-use case for it?
* maint set python auto-load.
Enable/disable the auto-loading of Python scripts when an object
file is opened.
I think this patch is dead. It has been superseded by a the more
generic and powerful gdb auto-load commands.
* require command.
This command loads on demand a Python script that registers a gdb
command and which has not been auto-loaded at start-up. This makes
it easier to load GDB commands written in Python.
* ignore_errors command.
A wrapper which executes a single command, ignoring and suppressing
all errors.
I think this patch is dead. Users can deal with these exceptions
independently.
* pahole command.
Show the holes in a structure. Takes a type. Comment on those areas
where it thinks it detects a hole.
I think this command is generally useful. I think I remember some
comments about some problems with it. I am hoping the discussion
regarding the problems can be rewritten and posted here.
* caller_is convenience function.
This function determines if the calling function's name is equal to
a string that is passed to it. It takes an optional argument to
traverse n stack frames to find the function.
I think this a useful convenience function. It returns Boolean
values, so is useful in GDB via the $ convenience variable
functionality. An additional option that would be useful would be
the ability to tell the function to traverse the entire stack.
* caller_matches convenience function.
Same as above, but use re.match for the comparison. I think this
functionality should be rolled into caller_is.
* in_scope convenience function.
Return true if all the given variables and macros provided to it are
in scope. This function takes a variable amount of arguments, and
will only Return true if all the arguments are in scope.
There are a few other bits and pieces in there. Most, as far as I can
determine, are just some orphaned bits of code.
So, lets decide what we want to port to upstream and what we can get
rid of.
Cheers,
Phil
next reply other threads:[~2013-10-14 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 11:26 Phil Muldoon [this message]
2013-10-14 14:38 ` Tom Tromey
2013-10-14 19:27 ` Phil Muldoon
2013-10-14 19:31 ` 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=525BD4EA.60907@redhat.com \
--to=pmuldoon@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).