On Sun, May 17, 2009 at 1:01 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Dave Page <dpage@pgadmin.org> writes:
>> Hmm, that was easier than I expected:
>
>> =A0 =A0 =A0 perl510.dll!PerlIOUnix_refcnt_inc(int fd=3D0) =A0Line 2339 =
=A0C
>> =A0 =A0 =A0 perl510.dll!PerlIOUnix_setfd(interpreter * my_perl=3D0x00000=
000,
>> _PerlIO * * f=3D0x00000000, int fd=3D0, int imode=3D0) =A0Line 2548 + 0xc
>> bytes C
>> =A0 =A0 =A0 perl510.dll!PerlIOUnix_open(interpreter * my_perl=3D0x002425=
44,
>> _PerlIO_funcs * self=3D0x280cb548, PerlIO_list_s * layers=3D0x012d3494,
>> long n=3D0, const char * mode=3D0x280be040, int fd=3D0, int imode=3D0, i=
nt
>> perm=3D0, _PerlIO * * f=3D0x00000000, int narg=3D0, sv * * args=3D0x0000=
0000)
>> Line 2626 =A0 =A0 C
>
> Hmmm ... you sure functions named like that should be getting called
> in a Windows build?
Well there are #ifdef WIN32 blocks in some of those PerlIOUnix
functions, so I assume they are expected to be used on Windows.
--=20
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
