#8601: Running alert with execl from app launched by tracker results in infinite loop ------------------------+------------------------------ Reporter: pulkomandy | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: System | Version: R1/Development Keywords: | Blocked By: Blocking: | Has a Patch: 0 Platform: All | ------------------------+------------------------------ Use this very simple application : {{{ int main(void) { execl("/bin/alert", "alert", "alert", "alert", NULL); } }}} When run from terminal, everying works as expected. When run from Tracker, alert gets launched, but apparently gets an invalid port. Notes from IRC chat about it : <AnEvilYak> alert's BApplication looper seems to have an invalid port <AnEvilYak> BLooper::ReadRawFromPort() calls port_buffer_size_etc() which returns a negative value <AnEvilYak> because of the way things are returned up the chain, this leads BLooper to think it has a message even though it doesn't Since alert is then sucking 100% CPU, this is quite annoying to debug on my single-core machine. -- Ticket URL: <http://dev.haiku-os.org/ticket/8601> Haiku <http://dev.haiku-os.org> Haiku - the operating system.