From: Doug Evans <xdje42@gmail.com>
To: Siva Chandra <sivachandra@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Debug Methods in GDB Python
Date: Fri, 06 Dec 2013 06:31:00 -0000 [thread overview]
Message-ID: <m3wqjize2h.fsf@sspiff.org> (raw)
In-Reply-To: <CAGyQ6gxe2UiMFJs6LDBxetc9ZDuhHj5uc0HP0Pd=ebqNdJ-_Mg@mail.gmail.com> (Siva Chandra's message of "Mon, 25 Nov 2013 17:25:00 -0800")
Siva Chandra <sivachandra@google.com> writes:
> Doug pointed out offlist that the ChangeLog was improperly done. Below
> is the corrected ChangeLog entry. For convenience, I have also
> attached the same patch that I have posted last time.
>
> 2013-11-25 Siva Chandra Reddy <sivachandra@google.com>
>
> Add Debug methods support in GDB Python.
>
> * Makefile.in: Add entries for new files.
> * data-directory/Makefile.in: Add entries for new Python files.
> * eval.c (evaluate_subexp_standard): Lookup and invoke methods
> defined in extension languages.
> * valarith.c (value_x_binop, value_x_unop): Lookup and invoke
> overloaded operator methods defined in extension languages.
> * valops.c (find_oload_method_list, find_method_list,
> find_overload_match, find_oload_champ): Lookup methods defined
> in extension languages.
> (value_has_indirect_dynamic_type): New function to determine
> the indirect dynamic type of a value.
> * value.h (find_overload_match): Update signature.
> * ext-function.c: New file.
> * ext-function.h: New file.
> * python/py-debugmethods.c: New file.
> * python/py-objfile.c (objfile_object): New field
> 'debug_methods'.
> (objfpy_dealloc): XDECREF on the new debug_methods field.
> (objfpy_new, objfile_to_objfile_object): Initialize
> debug_methods field.
> (objfpy_get_debug_methods): New function.
> (objfile_getset): New entry 'debug_methods'.
> * python/py-progspace.c (pspace_object): New field
> 'debug_methods'.
> (pspy_dealloc): XDECREF on the new debug_methods field.
> (pspy_new, pspace_to_pspace_object): Initialize
> debug_methods field.
> (pspy_get_debug_methods): New function.
> (pspace_getset): New entry 'debug_methods'.
> * python/python-internal.h: Add declarations for new functions.
> * python/python.c (_initialize_python): Invoke
> gdbpy_initialize_debugmethods.
> * python/python.h: Add declarations of new functions.
> * python/lib/gdb/__init__.py (debug_methods): New attribute.
> * python/lib/gdb/debugmethods.py: New file.
> * python/lib/gdb/command/debug-methods.py: New file.
>
> testuite/
> * gdb.python/py-debugmethods.cc: New testcase to test debug
> methods.
> * gdb.python/py-debugmethods.exp: New tests to test debug
> methods.
> * gdb.python/py-debugmethods.py: Python script supporting the
> new testcase and tests.
Sorry for the delay.
I've been wanting to find time to investigate some of the suggestions I made.
e.g., instead of DEFAULT_DEBUG_METHOD_GROUP, etc.
have the grouping work the same way it does for the libstdc++
pretty-printers. Have you thought about it?
next prev parent reply other threads:[~2013-12-06 6:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 22:41 Siva Chandra
2013-11-26 3:22 ` Siva Chandra
2013-12-06 6:31 ` Doug Evans [this message]
2013-12-06 23:24 ` Siva Chandra
2013-12-12 5:26 ` Doug Evans
2013-12-13 19:25 ` Siva Chandra
2013-12-16 17:56 ` Doug Evans
2013-12-16 22:43 ` Siva Chandra
2014-01-01 12:23 ` Siva Chandra
2014-01-03 18:52 ` Doug Evans
2014-01-08 0:49 ` Siva Chandra
2014-01-09 19:01 ` Doug Evans
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=m3wqjize2h.fsf@sspiff.org \
--to=xdje42@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.com \
/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).