[Development] Using platform-native APIs for terminating QThreads

[Viktor Engelmann]

It is just a (more extreme) example of my point:

If the user bypasses our security measures and shoots himself in the
foot - why should we take any responsibility for that?



Am 06.09.2016 um 01:44 schrieb Thiago Macieira:
> Em segunda-feira, 5 de setembro de 2016, às 16:08:41 PDT, Viktor Engelmann 
> escreveu:
>> So what if the user adds an asm statement that changes a register and
>> doesn't declare that register to be changed? That would also cause his
>> "Qt" application to misbehave... or what if he links the object files to
>> a custom loader that doesn't call the constructors for global objects?
> If you insert an asm statement that changes a register and you don't inform 
> GCC that you changed it, then your application is buggy and it deserves to 
> crash. In fact, you should HOPE it crashes cleanly, before it corrupts any 
> user data.
>
> Still, what does that have to do with the problem at hand?
>

-- 


Viktor Engelmann
Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
Viktor.Engelmann at qt.io
+49 151 26784521
http://qt.io

Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht
Charlottenburg, HRB 144331 B
<http://qt.io>
<http://www.facebook.com/Qt> 	<http://www.twitter.com/qtproject>
<https://www.linkedin.com/company/the-qt-company/>
<https://plus.google.com/104580575722059274792>
<https://www.youtube.com/QtStudios>

Qt World Summit 2016 <http://qtworldsummit.com/>
Qt World Summit 2016 | Pier 27, San Francisco, CA
Experience Exponential Potential on October 18-20
www.qtworldsummit.com <http://www.qtworldsummit.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160906/c3ea3d0e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt_logo_with_text_green_rgb_400x141.png
Type: image/png
Size: 16849 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160906/c3ea3d0e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt_facebook.png
Type: image/png
Size: 1407 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160906/c3ea3d0e/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt_twitter.png
Type: image/png
Size: 1778 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160906/c3ea3d0e/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt_linkedin.png
Type: image/png
Size: 1532 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160906/c3ea3d0e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt_googleplus.png
Type: image/png
Size: 1957 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160906/c3ea3d0e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qt_youtube.png
Type: image/png
Size: 1610 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160906/c3ea3d0e/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qtworldsummit2016_banner.jpg
Type: image/jpeg
Size: 35183 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160906/c3ea3d0e/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: viktor_engelmann.vcf
Type: text/x-vcard
Size: 271 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20160906/c3ea3d0e/attachment.vcf>