| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
This assures that TQRegExp who checks if there is an active thread
through this interface won't try to access its already destroyed
TQThreadLocalStorage, which might happen during destruction of static
TQRegExp objects.
Bug: https://mirror.git.trinitydesktop.org/gitea/TDE/tqt3/issues/142
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before that the allocations of TQThreadStorage objects from the main
thread were never destroyed and memory associated with them were never
freed. The second one isn't a huge problem as at that point program is
terminating anyway (but it still makes valgrind complain). The first one
is the bigger issue as destructors might contain some essential external
cleanups like removing temporary files.
Also make `TQApplication::guiThread()` return `0` when the thread is
destroyed (may happen on the program exiting during destruction of
statics).
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
|
|
|
|
|
|
| |
g_thread_init() and g_thread_create().
Signed-off-by: gregory guy <gregory-tde@laposte.net>
|
|
|
|
|
|
|
| |
If `_POSIX_THREAD_PRIORITY_SCHEDULING == 0`, it must be checked
with sysconf(_SC_THREAD_PRIORITY_SCHEDULING) at runtime.
Signed-off-by: OBATA Akio <obache@wizdas.com>
|
|
|
|
|
|
|
| |
qt->tqt conversion and is required to align to corresponding patch for
common/admin module.
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|