You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by szenker <gi...@git.apache.org> on 2016/01/18 09:35:21 UTC
[GitHub] thrift pull request: THRIFT-3564: potential core dump in TQTcpServ...
GitHub user szenker opened a pull request:
https://github.com/apache/thrift/pull/802
THRIFT-3564: potential core dump in TQTcpServer
TQTcpServer: it's not allowed to delete the sender of a Qt signal (QTcpSocket) while executing one of its slots. This could happen in TQTcpServer::beginDecode() in case an exception occurred. Ensured, that deletion is deferred in all cases.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/szenker/thrift THRIFT-3564
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/thrift/pull/802.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #802
----
commit 59de41dbb82da1ad5a426cb9a1fac55360e33229
Author: Sebastian Zenker <se...@gmx.de>
Date: 2016-01-18T07:45:52Z
C++/Qt: TQTcpServer: it's not allowed to delete the sender of a Qt signal (QTcpSocket) while executing one of its slots. This could happen in TQTcpServer::beginDecode() in case an exception occurred. Ensured, that deletion is deferred in all cases.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] thrift pull request: THRIFT-3564: potential core dump in TQTcpServ...
Posted by szenker <gi...@git.apache.org>.
Github user szenker closed the pull request at:
https://github.com/apache/thrift/pull/802
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---