Sander Temme <[email protected]> said: > > On May 31, 2009, at 3:31 AM, Bojan Smojver wrote: > >> On Sat, 2009-05-30 at 23:55 -0700, Sander Temme wrote: >>> #0 0x000103a7 in send0_pollset (tc=0xbffff508, data=0x0) at >>> testpoll.c:389 >> >> If you stop there and have a look at the vars, anything that GDB >> doesn't >> like? Wrong alignment and such? > > > I built a new copy with -O0. Make check gives me: > > testpoll : |/bin/sh: line 1: 54775 Bus error > (core dumped) ./$prog > Programs failed: testall > make[1]: *** [check] Error 138 > make: *** [check] Error 2 > > #0 0x0001213e in send0_pollset (tc=0xbffff564, data=0x0) at > testpoll.c:389 > #1 0x000024b4 in abts_run_test (ts=0x1001f0, f=0x12071 <send0_pollset>, > value=0x0) at abts.c:168 > #2 0x00013303 in testpoll (suite=0x1001f0) at testpoll.c:685 > #3 0x00002e4d in main (argc=1, argv=0xbffff5e8) at abts.c:424
What is the expected behavior of timeout == 0 of the APR poll APIs (apr_poll, apr_pollset_poll, etc)? Since poll() returns immediately when the timeout is zero, could this cause unexpected behavior within the testpoll application? Regards, Ryan
