Am 10.07.2013 um 02:09 schrieb Hamish Moffatt :
> On 09/07/13 17:00, Till Oliver Knoll wrote:
>> By the way: SIGTERM is the signal sent to a console application when
>> pressing CTRL + C (also on Windows).
> I think that's SIGINT actually, but I'm nitpicking..
Yeah, right :)
Trying to refresh m
On terça-feira, 9 de julho de 2013 15.13.55, Jonathan Greig wrote:
> Off of the top of my head, Qt typically doesn't allocate memory that the
> programmer is then explicitly required to free as long as the object is
> assigned a parent. If it does allocate memory that the programmer needs to
> free
Hi,
On Tuesday 09 July 2013 09:00:55 Till Oliver Knoll wrote:
> A) is by design: it is there to really *really* kill a process in the most
> brutal manner (*) a sysadmin could think of and a process being able to
> catch (and possibly ignore!) that signal would defeat its purpose.
> (*) which can
On terça-feira, 9 de julho de 2013 15.37.51, lucas.betsch...@crypto.ch wrote:
> Hi
>
> Since Qt already uses OpenSSL for networking are there any plans to add the
> encryption capabilities of OpenSSL (AES etc.) to Qt? So far there seems to
> be no regular encryption in Qt included.
We're forbidden
Thiago,
Show reachable is typically considered not a problem in most cases but it's
still good to know it's there. In the case of the unicode stuff it is
reporting, I do not want to see it and would be a possible candidate for
suppression. An example of what I am interested in seeing is this: I had
Hi
Since Qt already uses OpenSSL for networking are there any plans to add the
encryption capabilities of OpenSSL (AES etc.) to Qt?
So far there seems to be no regular encryption in Qt included.
Regards
___
Interest mailing list
Interest@qt-project.or
Hi,
In my application I have a custom QQuickItem that has time varying
parameters which are input externally from the C++ side of things. When the
QQuickItem renders, it grabs these parameters using a callback function
that shares memory with the main thread, so I need to protect any shared
memory
Am 09.07.2013 um 06:13 schrieb Charles Yin :
> see also :
> http://stackoverflow.com/questions/3360761/how-to-do-a-cleanup-after-sigkill
The answers tell you that
A) SIGKILL ("kill -9") can *not* be caught by a process and hence
B) If you *really* need to do cleanup in such a case you need to
