From: Michal Marek <mmarek@suse.cz>
To: Chris Bainbridge <chris.bainbridge@gmail.com>, yann.morin.1998@free.fr
Cc: linux-kernel@vger.kernel.org, bbarbulovski@gmail.com
Subject: Re: [PATCH] kconfig: fix qconf segfault by deleting heap objects
Date: Mon, 11 Jan 2016 09:46:41 +0100 [thread overview]
Message-ID: <56936BF1.9080800@suse.cz> (raw)
In-Reply-To: <20160108204404.GA14615@localhost>
On 2016-01-08 21:44, Chris Bainbridge wrote:
> On Debian stable (qt-4.8.6) 'make xconfig' intermittently fails due to
> qconf segfaulting at exit time in QXcbEventReader. The cause of this is
> destructors on the heap objects never being called, so fix this by
> properly deleting the heap objects before exit.
>
> Signed-off-by: Chris Bainbridge <chris.bainbridge@gmail.com>
> ---
> Trivial error, as described at https://forum.qt.io/topic/26658/solved-segfault-on-qapplication-exit
> ---
> scripts/kconfig/qconf.cc | 2 ++
> 1 file changed, 2 insertions(+)
Applied to kbuild.git#kconfig, thanks.
Michal
prev parent reply other threads:[~2016-01-11 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 20:44 [PATCH] kconfig: fix qconf segfault by deleting heap objects Chris Bainbridge
2016-01-11 8:46 ` Michal Marek [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=56936BF1.9080800@suse.cz \
--to=mmarek@suse.cz \
--cc=bbarbulovski@gmail.com \
--cc=chris.bainbridge@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.