| … | |
… | |
| 3408 | with any compiler warnings enabled unless you are prepared to cope with |
3408 | with any compiler warnings enabled unless you are prepared to cope with |
| 3409 | them (e.g. by ignoring them). Remember that warnings are just that: |
3409 | them (e.g. by ignoring them). Remember that warnings are just that: |
| 3410 | warnings, not errors, or proof of bugs. |
3410 | warnings, not errors, or proof of bugs. |
| 3411 | |
3411 | |
| 3412 | |
3412 | |
| 3413 | =head1 VALGRIND |
3413 | =head2 VALGRIND |
| 3414 | |
3414 | |
| 3415 | Valgrind has a special section here because it is a popular tool that is |
3415 | Valgrind has a special section here because it is a popular tool that is |
| 3416 | highly useful. Unfortunately, valgrind reports are very hard to interpret. |
3416 | highly useful. Unfortunately, valgrind reports are very hard to interpret. |
| 3417 | |
3417 | |
| 3418 | If you think you found a bug (memory leak, uninitialised data access etc.) |
3418 | If you think you found a bug (memory leak, uninitialised data access etc.) |
| … | |
… | |
| 3512 | involves iterating over all running async watchers or all signal numbers. |
3512 | involves iterating over all running async watchers or all signal numbers. |
| 3513 | |
3513 | |
| 3514 | =back |
3514 | =back |
| 3515 | |
3515 | |
| 3516 | |
3516 | |
| 3517 | =head1 PORTABILITY |
3517 | =head1 PORTABILITY NOTES |
| 3518 | |
3518 | |
| 3519 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
3519 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
| 3520 | |
3520 | |
| 3521 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
3521 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
| 3522 | requires, and its I/O model is fundamentally incompatible with the POSIX |
3522 | requires, and its I/O model is fundamentally incompatible with the POSIX |
