Re: [BUGS] BUG #6204: Using plperl functions generate crash

[ljwilson]

I began testing PostgreSQL 9.1.x last week, and came across this issue.
Repeatable under the following scenarios (all 32-bit)

1. Windows XP SP3 with latest updates.
2. Windows 7 SP1 with latest updates.
3. Any flavor of Perl 5.1.4.x (I've tried strawberry-perl-5.14.2.1-32bit,
ActivePerl-5.14.2.1402-MSWin32-x86-295342, and compiled my own for 5.14.0,
5.14.1, and 5.14.2)
4. postgresql-9.1.0-windows, postgresql-9.1.1-windows,
postgresql-9.1.2-windows, and postgresql-9.1.3-windows from the one-click
installers.
5. Compiled postgresql-9.1.3 from source using Windows Platform SDK 7.0.

But here is what will work:
1. Compile postgresql-9.1.3 using mingw32
2. Replace only the plperl.dll the official binaries supply with the
plperl.dll you get from the mingw32 compile
3. Then the test which started this bug discussion works.

This makes me think there is an incompatibility in some environments related
to plperl. I thought maybe it was the version of msvcr90.dll since the
mingw32 compile doesn't link with it. I've got four versions of it on my XP
test box, and have put each version of that dll in my various install
subdirectories (perl\bin, perl\lib, pgsql\bin, pgsql\lib), and none of them
make a difference (assuming it is seeing them "first"). 

My MSVCR90.DLL versions (size)
9.0.21022.8 (655,872 bytes)
9.0.30729.1 (655,872 bytes)
9.0.30729.4148 (653,120 bytes)
9.0.30729.6161 (653,136 bytes)

If it is an environment issue of some kind it would be interesting to know
what locales people have where it works versus where it doesn't. I'm using
the standard ones that the PostgreSQL one-click installer defaults to.

I'd be glad to post the plperl.dll (160,324 bytes) that works for me if
there is a proper place for this kind of thing. Or just compile it from
source yourself using the mingw instructions at
http://www.postgresql.org/docs/9.1/static/installation-platform-notes.html#INSTALLATION-NOTES-MINGW

...jack



--
View this message in context: 
http://postgresql.1045698.n5.nabble.com/BUG-6204-Using-plperl-functions-generate-crash-tp4802111p5651759.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Re: [BUGS] BUG #6204: Using plperl functions generate crash

[ljwilson]

Follow-up:

Putting in debug stubs for the plperl.c source from PostgreSQL 9.1.3 I've
determined the crash mentioned in the first post of this thread occurs at
line 905:
if (SvTRUE(ERRSV))

Googling I found this:

http://www.perlmonks.org/?node_id=870835

Where the last post in the thread talks about mismatches between MSVCR80.dll
and MSVCRT.DLL causing the same crash in Perl 5.10. I think we have the same
issue here between ActiveState Perl using MSVCRT.DLL and PLPERL.DLL compiled
with the MS compilers using MSVCR90.DLL.

So another solution which I've tested (and it works for me) is to compile
Perl 5.14.2 from source using the Windows Platform SDK 7.0 (same one I used
to compile PostgreSQL 9.1.3 in my previous post). To do that I changed the
CCTYPE = MSVC90 in \win32\Makefile. This forces Perl
to use the same MSVCR90.DLL that PLPERL.DLL (and PostgreSQL itself) uses.

What I still don't understand is why ActiveState 5.14.1 and 5.14.2 work for
some people with the official Postgresql 9.1.x binaries and not others.

Since I distribute my own compiled version of Perl anyway, for PostgreSQL
9.1.x I will simply compile Perl with the Windows Platform SDK 7.0 instead
of mingw32.

--
View this message in context: 
http://postgresql.1045698.n5.nabble.com/BUG-6204-Using-plperl-functions-generate-crash-tp4802111p5654505.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs