wrote:
> What's that? Is it portable?
>
> -aaron
>
> On Wednesday, July 30, 2003, at 01:01 PM, Joshua Moore-Oliva wrote:
> > I may eb way out of the ball park here but as far as the line
> >
> > mutex->owner_ref++
> >
> > is concerned.. couldn't owner be a sig_atomic_t?
The document reads.
@param hostname The hostname or numeric address string to resolve/parse, or
* NULL to build an address that corresponds to 0.0.0.0 or ::
However, it only works if I pass APR_ANYADDR which makes sense since it's
defined as 0.0.0.0
Josh.
I got the following segmentation fault and core dump with apr..
I am using glibc version 2.3.1
Output below.
Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain condit
Yep, thanks and I should have clarified in my response that I wasn't sure
whether it was for earlier reasons or just a we've already set a spec.
Josh.
On July 10, 2003 06:26 pm, Cliff Woolley wrote:
> On Thu, 10 Jul 2003, Joshua Moore-Oliva wrote:
> > Regardless of it&
> All you have to do is get rid of those two apr_pool_destroy() lines and it
> will work fine. You can go ahead and free(t) in your cleanup function.
> Then when you cleanup "pool", read_pool and write_pool will be cleaned up
> and then t will be freed.
>
> The point is that you should never regi
Currently in apr_pool_destroy there is this chunk of code
while (pool->child)
apr_pool_destroy(pool->child);
run_cleanups(&pool->cleanups);
The problem here is if I created a subpool for temporary scratch space, then
registered that subpool as a cleanup the pool will be cleaned u
When I compile with -ansi in my CFLAGS, I get
/usr/local/apr/include/apr-0/apr.h:428:2: #error no decision has been made on
APR_PATH_MAX for your platform
However, when ansi is off it works...
does anyone have an idea why this is the case? I tend to like the safety of
ansi.
Josh.
Right now these two entries read...
/**
* put a character into the specified file.
* @param ch The character to write.
* @param thefile The file descriptor to write to
*/
APR_DECLARE(apr_status_t) apr_file_putc(char ch, apr_file_t *thefile);
/**
* get a character from the specified file.
*
Is apr threadsafe? I won't be using a single pool between multiple threads...
but I do plan on calling apr_initialise once in main before launching my
threads..
Are there any gotchas (apart from gdbm) thread-wise that I should look out
for, or is apr thread safe?
Josh
WIll 0.9.3 be considered to be out of alpha when it is released?
I've been watching this project with great interest for quite a while, thogh
I'm a little scared to use alpha code.
Josh.
On June 11, 2003 11:45 pm, Rodent of Unusual Size wrote:
> APRUTIL LIBRARY STATUS:
I think that would be a great idea... As long as apr still came bundled
into apache, I woul dhave tons of uses for apr separate from apache.
Josh.
On Mon, 2002-09-09 at 02:47, Aaron Bannert wrote:
> [sorry for the crosspost. I'm moving this branch of the conversation
> to the [EMAIL PROTECTED] l
I have noticed that the of apr_file_seek uses apr_file_flush in the
setptr argument. I have an operation that only writes to a buffered
file, and yes I must change file position while doing a write only
operation, and the file_flush consumes a lot of time.
In the following source code, could anyo
12 matches
Mail list logo
