On Wed, Jun 17, 2009 at 2:54 AM, Bojan Smojverbo...@rexursive.com wrote:
On Tue, 2009-06-16 at 00:41 +0200, Jack Andrews wrote:
feedback welcome - it can probably be improved
Did you really want to use functions for casting?
removed the casting functions:
Index:
Hi Jack,
Regardless of the portability library that you're using, Windows
doesn't allow select() operations on any other than socket handles.
I don't have personal experience how to work around that issue with
APR though, I'm sorry.
With kind regards,
Erik.
On Tue, Jun 16, 2009 at 8:42 PM,
just realized that i no longer need the additional redirection here:
[i'll send another patch including any other feedback i might get]
@@ -159,6 +159,8 @@
apr_pool_t *p,
apr_uint32_t flags)
{
+ struct
Jack Andrews wrote:
hi,
i want to detect IO on a child process stdio as well
as a socket from elsewhere. ie. i want a select()
on /windows/.
is it possible with APR? or do i have to hack around?
It's not possible with APR, however you can make a hack
if you know its stdin (or stdout,
i want to detect IO on a child process stdio as well
as a socket from elsewhere. ie. i want a select()
on /windows/.
i wonder if it would be useful to have an
apr_socket_from_files(files_in, files_out, socket)
that plugs a socket onto the end of pipes on windows.
. only implement on
Hi all,
I've hit a segfault trying to build APR 1.3.5 on AIX 5.3.
I configured APR with: --enable-shared=no --enable-static=yes
--enable-threads
The segfault is triggered by the testlockperf (other tests fail similarly)
with the following bt:
#0 apr_proc_mutex_unix_setup_lock () at
On Thu, 2009-06-18 at 00:51 +0200, Gavin Sherry wrote:
497 proc_mutex_unlock_it.l_pid = 0; /* pid not
actually interesting */
What's in proc_mutex_unlock_it when this happens? What's its size?
Can you tell us what your fcntl.h holds for struct flock?
PS. I do not have access
2009/6/18 Bojan Smojver bo...@rexursive.com
On Thu, 2009-06-18 at 00:51 +0200, Gavin Sherry wrote:
497 proc_mutex_unlock_it.l_pid = 0; /* pid not
actually interesting */
What's in proc_mutex_unlock_it when this happens? What's its size?
$1 = {l_type = 0, l_whence = 0,
On Thu, 2009-06-18 at 02:18 +0200, Gavin Sherry wrote:
$2 = 24
ptype proc_mutex_unlock_it
type = struct flock {
short l_type;
short l_whence;
off_t l_start;
off_t l_len;
unsigned int l_sysid;
pid_t l_pid;
int l_vfs;
}
I'm guessing here: short 2 bytes, off_t
2009/6/18 Bojan Smojver bo...@rexursive.com
On Thu, 2009-06-18 at 02:18 +0200, Gavin Sherry wrote:
$2 = 24
ptype proc_mutex_unlock_it
type = struct flock {
short l_type;
short l_whence;
off_t l_start;
off_t l_len;
unsigned int l_sysid;
pid_t l_pid;
On Thu, 2009-06-18 at 02:45 +0200, Gavin Sherry wrote:
No, it comes to 24 bytes. short = 2 + 2, off_t = 4 + 4, + 4 + 4 + 4 =
24. off_t = 4 for this build because I've forced it to 32 bit (gcc
-m32) based on some other requirements.
OK. Hmm, interesting. So, it segfaults on assigning l_pid.
2009/6/18 Bojan Smojver bo...@rexursive.com
On Thu, 2009-06-18 at 02:45 +0200, Gavin Sherry wrote:
No, it comes to 24 bytes. short = 2 + 2, off_t = 4 + 4, + 4 + 4 + 4 =
24. off_t = 4 for this build because I've forced it to 32 bit (gcc
-m32) based on some other requirements.
OK. Hmm,
On Thu, 2009-06-18 at 03:12 +0200, Gavin Sherry wrote:
It's a little late my time to decipher this.
I'll bet on of of the load/store thingies. Try with si/ni to determine
where exactly it dies. Yeah, I know - not much help :-(
--
Bojan
13 matches
Mail list logo
