From: Phil Muldoon <pmuldoon@redhat.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [RFC - Python] New ObjFile event
Date: Wed, 30 Mar 2011 12:14:00 -0000 [thread overview]
Message-ID: <m339m4dgzr.fsf@redhat.com> (raw)
In-Reply-To: <AANLkTi=ObZFW+uoecfzvHhXr55zYZzSgX2ocJJrvXDv0@mail.gmail.com> (Kevin Pouget's message of "Wed, 30 Mar 2011 05:24:44 -0400")
Kevin Pouget <kevin.pouget@gmail.com> writes:
> Hello,
>
> here is a patch with all the modifications we discussed so far,
> including the ChangeLog entry and the new files
>
Really nice patch!
Just one tiny nit...
> gdb/ChangeLog | 28 +++++++++++++++
This is the ChangeLog for GDB code, so things in gdb/ and python/ code
related files have ChangeLog entries here.
> @@ -1,3 +1,31 @@
> +2011-03-29 Kevin Pouget <kevin.pouget@st.com>
> +
> + Allow Python notification of new object-file loadings
> + * Makefile.in (SUBDIR_PYTHON_SRCS): Add py-newobjfilevent.c.
> + (SUBDIR_PYTHON_OBS): Add py-newobjfileevent.o.
> + Add build rule for this file.
> + * python/py-event.h (emit_new_objfile_event): New prototype.
> + (newobjfile): New Python event emitter.
> + * python/py-evts.c (gdbpy_initialize_py_events): Add newobjfile to
> + Python event registry.
> + * python/py-inferior.c: Include objfiles.h
> + (python_new_objfile): New function.
> + (gdbpy_initialize_inferior): Add python_new_objfile to the new objfile
> + observers.
> + * python/py-newobjfileevent.c: New file.
> + * python-internal.h (gdbpy_initialize_new_objfile_event): New
> + prototype.
> + (gdbpy_current_objfile): New global variable.
> + * python/python.c (gdbpy_current_objfile): Make global.
> + (_initialize_python): Add gdbpy_initialize_new_objfile_event call.
But the entries below belong in the testsuite/ChangeLog and without the
preceding "testsuite" in the log.
> + * testsuite/gdb.python/py-events-shlib.c: New file.
> + * testsuite/gdb.python/py-events.c (do_nothing): New global.
> + (main): Add call to shared library.
> + * testsuite/gdb.python/py-events.exp: Link the execfile to a shared
> + library and check newobjfile event notification.
> + * testsuite/gdb.python/py-events.py (new_objfile_handler): New Class.
> + (test_newobj_events): New class.
> +
I don't see a documentation entry. Similarly documentation entries are
added in the doc/ChangeLog
But this patch looks great. Tom or another maintainer will look at it
soon.
Cheers
Phil
next prev parent reply other threads:[~2011-03-30 10:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimybJtpUzy13FuLxQQMJfeWQuf3-cgqGmu23Bq5@mail.gmail.com>
2011-03-28 8:49 ` Kevin Pouget
2011-03-28 8:51 ` Kevin Pouget
2011-03-28 9:00 ` Phil Muldoon
2011-03-28 8:54 ` Phil Muldoon
2011-03-28 9:03 ` Phil Muldoon
2011-03-28 10:02 ` Kevin Pouget
2011-03-28 20:28 ` Tom Tromey
2011-03-29 11:11 ` Kevin Pouget
2011-03-30 11:32 ` Kevin Pouget
2011-03-30 12:14 ` Phil Muldoon [this message]
2011-03-30 12:15 ` Kevin Pouget
2011-05-19 20:21 ` Tom Tromey
2011-05-23 8:44 ` Kevin Pouget
2011-09-01 9:56 ` Kevin Pouget
2011-09-01 11:01 ` Eli Zaretskii
2011-09-01 11:09 ` Kevin Pouget
2011-10-03 16:32 ` Tom Tromey
[not found] ` <CAPftXULEe9R4m7tF=vtJe6NTXHSFAkXgsHCPb3r0mU4wKx0FFg@mail.gmail.com>
2011-10-04 8:25 ` Kevin Pouget
2011-10-04 17:02 ` Tom Tromey
2011-10-05 11:10 ` Kevin Pouget
2011-10-05 14:16 ` Tom Tromey
2011-10-05 17:40 ` Eli Zaretskii
2011-10-07 7:40 ` Kevin Pouget
2011-10-07 7:54 ` Kevin Pouget
2011-10-07 8:37 Andreas Tobler
2011-10-07 8:44 ` Kevin Pouget
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=m339m4dgzr.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevin.pouget@gmail.com \
--cc=tromey@redhat.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