| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
a client has closed connection prematurely
|
|
|
|
| |
*) of.failed to return exact name of failed syscall
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
the bug was introduced in r2564
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
*) master exit hook is run before global pool cleanup, so call PERL_SYS_TERM()
after perl_destruct()/perl_free(). This fixes the message
panic: MUTEX_LOCK (22) [op.c:352]
on some threaded perl builds
*) call perl_destruct()/perl_free() before PERL_SYS_TERM() for
non-mulitiplicity perl
|
|
|
|
| |
the bug has been introduced in r1947
|
|
|
|
| |
the bug has been introduced in r1259
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|