Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
pthread_exit seems to have been adopted as some trend in the early days of glibc 2.2.5 based on https://bugs.mysql.com/bug.php?id=82886 and the dates of initial pthread_exit call inclusions.
These seem to have been copied without much consideration.
This task takes a bit of debt back and just leaves our threads to exit, with the args that where being provided to pthread_exit,
This backports the removal and cleanup performed in the 11.4 merge - 2719cc4925c032f483edb0e61c0f487e0c429ae6
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | Daniel Black [ danblack ] | Marko Mäkelä [ marko ] |
Status | In Progress [ 3 ] | In Review [ 10002 ] |
Assignee | Marko Mäkelä [ marko ] | Daniel Black [ danblack ] |
Status | In Review [ 10002 ] | Stalled [ 10000 ] |
Summary | remove obsolete pthread_exit calls | remove pthread_exit calls that caused msan/libstdc++ clang19 problems |
Fix Version/s | 10.5.28 [ 29952 ] | |
Fix Version/s | 10.5 [ 23123 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Summary | remove pthread_exit calls that caused msan/libstdc++ clang19 problems | remove pthread_exit calls that caused msan/libc++ clang19 problems |
what's wrong with using pthread_exit()? it's not documented as obsolete, why should it be removed?