diff options
| author | Nick Mathewson <nickm@torproject.org> | 2010-09-15 01:08:39 -0400 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2010-09-15 01:12:01 -0400 |
| commit | 720bd933c8a4e9f0b850be075e055eea98767665 (patch) | |
| tree | fbea95ec2aa21a50d566681350af35fbb90ff361 /test/regress.c | |
| parent | 040a019f52a7933b2478fe41c3ab0b56835012b1 (diff) | |
| download | libevent-720bd933c8a4e9f0b850be075e055eea98767665.tar.gz | |
Warn when using the error-prone EV_SIGNAL interface in an error-prone way. Also, fix a couple of race conditions in signal.c
When using the signal.c signal backend, Libevent currently only allows
one event_base to actually receive signals at a time. (This has been
the behavior since at least 1.4 and probably much earlier.) Now, we
detect and warn if you're likely to be racing about which signal goes
to which thread.
We also add a lock to control modifications of the evsig_base field,
to avoid race conditions like those found by Jason Toffaletti.
Also, more comments. Comments are good.
Diffstat (limited to 'test/regress.c')
| -rw-r--r-- | test/regress.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/regress.c b/test/regress.c index 94bab8cc..d24992a8 100644 --- a/test/regress.c +++ b/test/regress.c @@ -2251,7 +2251,7 @@ struct testcase_t signal_testcases[] = { LEGACY(immediatesignal, TT_ISOLATED), LEGACY(signal_dealloc, TT_ISOLATED), LEGACY(signal_pipeloss, TT_ISOLATED), - LEGACY(signal_switchbase, TT_ISOLATED), + LEGACY(signal_switchbase, TT_ISOLATED|TT_NO_LOGS), LEGACY(signal_restore, TT_ISOLATED), LEGACY(signal_assert, TT_ISOLATED), LEGACY(signal_while_processing, TT_ISOLATED), |