diff options
| author | Bradley T. Hughes <bradley.hughes@nokia.com> | 2010-10-06 08:31:06 (GMT) |
|---|---|---|
| committer | Bradley T. Hughes <bradley.hughes@nokia.com> | 2010-10-06 10:52:47 (GMT) |
| commit | ccd3f663c8c96e266b173a6f825bccec830007e1 (patch) | |
| tree | c9f83240bcd5f2bca58d9733aa5fac4f8e78ec57 /bin | |
| parent | e98962aab2db1c3760b324d6640fa8b510b7e04c (diff) | |
| download | Qt-ccd3f663c8c96e266b173a6f825bccec830007e1.zip Qt-ccd3f663c8c96e266b173a6f825bccec830007e1.tar.gz Qt-ccd3f663c8c96e266b173a6f825bccec830007e1.tar.bz2 | |
Fix crash when constructing QThreadStorage after global destructors have run
In this particular case, the destructors vector used by
QThreadStorageData has already been destroyed, yet a new QThreadStorage
is being allocated. This can only happen during global destruction, at
which point we assume that there is only one thread. In order to keep
QThreadStorage working, we need somewhere to store the data, and the
best place we have in this situation is at the tail of the current
thread's tls vector. The destructor is ignored, since we have no where
to store it, and no way to actually call it.
Task-number: QTBUG-10084
Reviewed-by: thiago
Reviewed-by: olivier
Diffstat (limited to 'bin')
0 files changed, 0 insertions, 0 deletions