| Anonymous | Login | Signup for a new account | 11-10-2008 11:20 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0001551 | [uClibc] Standards Compliance | block | always | 10-23-07 00:18 | 12-30-07 12:22 | ||||
| Reporter | jcdr | View Status | public | ||||||
| Assigned To | uClibc | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | 0.9.28.1 | ||||||
| Summary | 0001551: Poll with zero or negative timeout | ||||||||
| Description |
Hello, I tried to use the bug tracking system, but the "Report Issue" page never go after the "Select Project" form. So I post this patch here. The attached patch solve an issue I faced while using the libdbus-glib waiting for a D-Bus message or the end of a glib timer at the same time. This specific case of use generate a poll call with a zero timeout. On platformes with the glibc a zero timeout poll return immetiately even if there is no file descriptor event. But on platformes with uClibc a zero timeout poll block until a file descriptor event occurs. I found that the file libc/sysdeps/linux/common/poll.c only take care of positive timeout and pass a null pointer in case of a zero or negative timeout, making the zero and negative the same case: blocking. The patch alway pass a valid structure for the timeout of poll and assign acceptable timeout values for the zero and negative case by avoiding the math needed for positive timeout value. This has been tested on a Blackfin BF533 processor. Have a good day, -- Jean-Christian de Rivaz |
||||||||
| Additional Information | |||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
Notes |
|
|
(0002858) jcdr 10-23-07 04:07 |
Joakim Tjernlund a |
|
(0002859) jocke 10-23-07 11:07 |
fixed in uClibc trunk |
| Copyright © 2000 - 2006 Mantis Group |