Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#44036 - [inotify-tools] inotifytools_next_event is blocking with 0 as time argument
Attached to Project:
Community Packages
Opened by Arne Döring (krux02) - Tuesday, 03 March 2015, 22:38 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 04 March 2015, 12:31 GMT
Opened by Arne Döring (krux02) - Tuesday, 03 March 2015, 22:38 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 04 March 2015, 12:31 GMT
|
DetailsDescription:
inotifytools_next_event should be non-blocking, when time is 0, as described here: http://inotify-tools.sourceforge.net/api/inotifytools_8h.html#2e121fde1cac7875d25a7e6c3bc57e1a. But it is blocking. Additional info: * package version community/inotify-tools 3.14-3 Steps to reproduce: git clone git@bitbucket.org:krux02/inotifytools_bug.git cd inotifytools_bug make ./a.out The program should exit immediately, because inotifytools_next_event() should return nullptr when there is no event queued up. But instead it just blocks forever. |
This task depends upon