Message from discussion plparrot/perl6
Received: by 10.150.252.14 with SMTP id z14mr4384057ybh.1.1276793210300;
Thu, 17 Jun 2010 09:46:50 -0700 (PDT)
Received: by 10.151.93.13 with SMTP id v13ls815618ybl.2.p; Thu, 17 Jun 2010
09:46:49 -0700 (PDT)
Received: by 10.150.132.17 with SMTP id f17mr4395317ybd.9.1276793209636;
Thu, 17 Jun 2010 09:46:49 -0700 (PDT)
Received: by 10.150.132.17 with SMTP id f17mr4395315ybd.9.1276793209572;
Thu, 17 Jun 2010 09:46:49 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [22.214.171.124])
by gmr-mx.google.com with ESMTP id v5si7952090ybk.13.2010.06.17.09.46.48;
Thu, 17 Jun 2010 09:46:48 -0700 (PDT)
Received-SPF: pass (google.com: domain of jal...@gmail.com designates 126.96.36.199 as permitted sender) client-ip=188.8.131.52;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jal...@gmail.com designates 184.108.40.206 as permitted sender) smtp.mail=jal...@gmail.com; dkim=pass (test mode) header...@gmail.com
Received: by gwj16 with SMTP id 16so113250gwj.3
for <email@example.com>; Thu, 17 Jun 2010 09:46:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
DomainKey-Signature: a=rsa-sha1; c=nofws;
Received: by 10.151.95.31 with SMTP id x31mr12643101ybl.2.1276793207154; Thu,
17 Jun 2010 09:46:47 -0700 (PDT)
Received: by 10.151.12.6 with HTTP; Thu, 17 Jun 2010 09:46:30 -0700 (PDT)
From: Jonathan Leto <jal...@gmail.com>
Date: Thu, 17 Jun 2010 09:46:30 -0700
Subject: Re: plparrot/perl6
Content-Type: text/plain; charset=windows-1252
Could you run "gdb postgres core" on the core file that generates? You
may have to stop Postgres,
and set "ulimit -c unlimited", and then restart Postgres to get core
files generated. They will drop
into the data directory of your Postgres database.
Once you are in "gdb", can you type "bt<enter>" to generate a backtrce
and send the output to the list?
PS: Also, the output of "uname -a" would be useful too.
On Thu, Jun 17, 2010 at 12:39 AM, Hitoshi Harada <umi.tan...@gmail.com> wro=
> 2010/6/16 Jonathan Leto <jal...@gmail.com>:
>> The warnings are due to bugs in Parrot, some functions are not listed
>> in the public-facing header files.
> Yep, and that causes call convention mismatch as below.
>> I don't use "make installcheck" much, i usually run "make test". What
>> exact output did you get? Installcheck might be broke.
> [plparrot]$ make test
> Found a sufficiently new version of Parrot r47271
> ./bin/text2macro.pl plparrot_secure.pir > plparrot.h
> ./bin/text2macro.pl plperl6.pir > plperl6.h
> \n\n\tHappy Hacking with PL/Parrot!\n\n
> psql -AX -f t/sql/test.sql
> psql:plparrot.sql:3: server closed the connection unexpectedly
> =A0 =A0 =A0 =A0This probably means the server terminated abnormally
> =A0 =A0 =A0 =A0before or while processing the request.
> psql:plparrot.sql:3: connection to server was lost
> make: *** [test] Error 2
> From what I looked at it is in _PG_init(). The return address from
> parrot API is bogus.
>> Also, it is always helpful to say which SHA1 of a branch you were
>> using, as well as the version of Postgres and Parrot
>> that are involved. The term "trunk" or HEAD constantly change, so
>> using specific revision numbers and SHA1's is best.
> PostgreSQL =3D> 9.0b2
> [parrot-head] $ svn info
> Path: .
> URL: https://svn.parrot.org/parrot/trunk
> Repository Root: https://svn.parrot.org/parrot
> Repository UUID: d31e2699-5ff4-0310-a27c-f18f2fbe73fe
> Revision: 47271
> Node Kind: directory
> Schedule: normal
> Last Changed Author: moritz
> Last Changed Rev: 47265
> Last Changed Date: 2010-06-02 05:49:16 +0900 (Wed, 02 Jun 2010)
> [plparrot] $ git info
> commit bfef901baa4e084c8319a9127b590d6175357dc4
> Author: Duke Leto <jonat...@leto.net>
> Date: =A0 Wed Jun 16 21:57:59 2010 -0700
> =A0 =A0Dump the return value with dumper.pbc
>> On Sun, Jun 13, 2010 at 2:24 AM, Hitoshi Harada <umi.tan...@gmail.com> w=
>>> So, I've been trying perl6 branch today, and found it cannot be built
>>> with parrot HEAD.
>>> plparrot.c:512: warning: implicit declaration of function
>>> Actually make is ok with bunch of warnings such as above, but make
>>> installcheck fails with CREATE FUNCTION. My conclusion is parrot
>>> functions like Parrot_str_new_constant() has special call convention,
>>> which results in the return address is missing without the correct
>>> #include when compiling.
>>> I tried many ways to build to succeed #include by randomly relocating
>>> *.h in the head of plparrot.c, though there seems almost no way. The
>>> only way I can see is to separate parrot-related APIs to another .c
>>> file (i.e. plparrot_misc.c) and to keep plparrot.c clean. If this
>>> approach is on the right way, I'll work by forking perl6 branch but
>>> not sure it is.
>>> Hitoshi Harada
>> Jonathan "Duke" Leto
> Hitoshi Harada
Jonathan "Duke" Leto