From: Simon Marchi <simon.marchi@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@ericsson.com>
Subject: [PATCH 0/5] Improve Python Inferior reference handling + fix a bug
Date: Mon, 23 Jan 2017 22:43:00 -0000 [thread overview]
Message-ID: <20170123224004.8893-1-simon.marchi@ericsson.com> (raw)
As I was investigating a crash related to Python Inferior objects, I saw some
opportunities to make the code a bit nicer/robust. This series is the result.
Simon Marchi (5):
Introduce specialized versions of gdbpy_ref
Add Python Inferior object debug traces
Make Python inferior-related internal functions return
inferior_object*
Make Python inferior-related internal functions return a gdbpy_inf_ref
Add missing incref when creating Inferior Python object
gdb/python/py-exitedevent.c | 4 +--
gdb/python/py-inferior.c | 73 ++++++++++++++++++++++++++------------------
gdb/python/py-infthread.c | 8 +++--
gdb/python/py-ref.h | 40 +++++++++++++++++++++---
gdb/python/python-internal.h | 13 ++++++--
gdb/python/python.c | 12 ++++++++
6 files changed, 110 insertions(+), 40 deletions(-)
--
2.11.0
next reply other threads:[~2017-01-23 22:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 22:43 Simon Marchi [this message]
2017-01-23 22:43 ` [PATCH 3/5] Make Python inferior-related internal functions return inferior_object* Simon Marchi
2017-01-24 0:03 ` Pedro Alves
2017-01-23 22:43 ` [PATCH 5/5] Add missing incref when creating Inferior Python object Simon Marchi
2017-02-25 18:41 ` Simon Marchi
2017-04-27 21:13 ` [pushed master+8.0] " Simon Marchi
2017-01-23 22:43 ` [PATCH 2/5] Add Python Inferior object debug traces Simon Marchi
2017-01-23 22:43 ` [PATCH 1/5] Introduce specialized versions of gdbpy_ref Simon Marchi
2017-01-24 15:54 ` Tom Tromey
2017-01-24 16:18 ` Simon Marchi
2017-02-09 11:58 ` Pedro Alves
2017-02-09 16:18 ` Simon Marchi
2017-01-23 22:43 ` [PATCH 4/5] Make Python inferior-related internal functions return a gdbpy_inf_ref Simon Marchi
2017-01-24 16:15 ` Simon Marchi
2017-02-09 12:30 ` Pedro Alves
2017-02-09 16:39 ` Simon Marchi
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=20170123224004.8893-1-simon.marchi@ericsson.com \
--to=simon.marchi@ericsson.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