|author||Rich Felker <firstname.lastname@example.org>||2012-02-27 18:51:02 -0500|
|committer||Rich Felker <email@example.com>||2012-02-27 18:51:02 -0500|
work around "signal loses thread pointer" issue with "approach 2"
this was discussed on the mailing list and no consensus on the preferred solution was reached, so in anticipation of a release, i'm just committing a minimally-invasive solution that avoids the problem by ensuring that multi-threaded-capable programs will always have initialized the thread pointer before any signal handler can run. in the long term we may switch to initializing the thread pointer at program start time whenever the program has the potential to access any per-thread data.
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions