GME  13
Bug List
Member APR_DECLARE (void) apr_sleep(apr_interval_time_t t)

write_fd duplicates the proc->out stream, it's really redundant and should be replaced in the APR 1.0 API with a bitflag of which proc->in/out/err handles should be health checked.

no platform currently tests the pipes health.

Member APR_DECLARE (void) apr_sleep(apr_interval_time_t t)

write_fd duplicates the proc->out stream, it's really redundant and should be replaced in the APR 1.0 API with a bitflag of which proc->in/out/err handles should be health checked.

no platform currently tests the pipes health.

Member APR_DECLARE (void) apr_sleep(apr_interval_time_t t)

write_fd duplicates the proc->out stream, it's really redundant and should be replaced in the APR 1.0 API with a bitflag of which proc->in/out/err handles should be health checked.

no platform currently tests the pipes health.

Member APR_DECLARE )(void) apr_pool_pre_cleanup_register(apr_pool_t *p

Some platforms cannot toggle between blocking and nonblocking, and when passing a pipe as a standard handle to an application which does not expect it, a non-blocking stream will fluxor the client app.

With versions 1.4.2 and prior on Windows, a call with no descriptors and timeout will return immediately with the wrong error code.

With versions 1.4.2 and prior on Windows, a call with no descriptors and timeout will return immediately with the wrong error code.

With versions 1.4.2 and prior on Windows, a call with no descriptors and timeout will return immediately with the wrong error code.

*end breaks type safety; where *buf is const, *end needs to be declared as const in APR 2.0

Note that calling this function with two NULL files on some platforms creates an APR_FULL_BLOCK pipe, but this behavior is neither portable nor is it supported.

Note that calling this function with two NULL files on some platforms creates an APR_FULL_BLOCK pipe, but this behavior is neither portable nor is it supported.

Note that calling this function with two NULL files on some platforms creates an APR_FULL_BLOCK pipe, but this behavior is neither portable nor is it supported.

Passing proc as a *proc rather than **proc was an odd choice for some platforms... this should be revisited in 1.0

Member APR_FILEPATH_NOTABOVEROOT
in APR 0.9 and 1.x, this flag's behavior is undefined if the rootpath is NULL or empty. In APR 2.0 this should be changed to imply NOTABSOLUTE if the rootpath is NULL or empty.
Member APU_DECLARE (apr_status_t) apr_dbm_open_ex(apr_dbm_t **dbm
In apr-util 0.9 and 1.x, the type arg was case insensitive. This was highly inefficient, and as of 2.x the dbm name must be provided in the correct case (lower case for all bundled providers)