From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix crash when using PYTHONMALLOC=debug (PR python/24742)
Date: Fri, 28 Jun 2019 20:34:00 -0000 [thread overview]
Message-ID: <87imsplaa6.fsf@redhat.com> (raw)
In-Reply-To: <87k1d5zqfg.fsf@tromey.com> (Tom Tromey's message of "Fri, 28 Jun 2019 09:21:23 -0600")
On Friday, June 28 2019, Tom Tromey wrote:
>>>>>> "Sergio" == Sergio Durigan Junior <sergiodj@redhat.com> writes:
>
> Sergio> gdb/ChangeLog:
> Sergio> 2019-06-27 Sergio Durigan Junior <sergiodj@redhat.com>
>
> Sergio> PR python/24742
> Sergio> https://bugzilla.redhat.com/show_bug.cgi?id=1723564
> Sergio> * python/python.c (do_start_initialization): Use 'xmalloc'
> Sergio> instead of 'PyMem_Malloc'.
>
> This is ok. Thanks for doing this. I appreciated your explanation as
> well.
Thank you, Tom.
Pushed: 5af5392a3d1525fb825747b203a6159ddcba0aa4
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2019-06-28 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 20:34 Sergio Durigan Junior
2019-06-28 15:21 ` Tom Tromey
2019-06-28 20:34 ` Sergio Durigan Junior [this message]
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=87imsplaa6.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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