plparrot/perl6 - plparrot

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion plparrot/perl6
Received-SPF: pass (google.com: domain of jal...@gmail.com designates 74.125.83.44 as permitted sender) client-ip=74.125.83.44;
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=wcq7T/NalhaB8zO+SBHJNgXo4YH4/a+UeFXxTD7M3maN4movJ4wwdj0/syFJQF6wMB
         xlo7NUIHo7kA+7/LRjf5dOv+HS3/OfIpBCLpaVhDPOyZ6gDKswP1hhCmRCJUn2rzO/O9
         psRCgIrvJXILEXcg8CYtu/IzPdIECy2i1bW+E=
MIME-Version: 1.0
In-Reply-To: <AANLkTikvH5jTDJ0yMojvZw5gJux-F10WQbV78lpZp...@mail.gmail.com>
References: <AANLkTinAJ2wjhGXc7uvNXDp2JGuI8J7Kn7xc9TLBr...@mail.gmail.com> 
	<AANLkTimq2KmiuLDbzto5kjCGcGTcXZnd_njO81D_3...@mail.gmail.com> 
	<AANLkTikvH5jTDJ0yMojvZw5gJux-F10WQbV78lpZp...@mail.gmail.com>
From: Jonathan Leto <jal...@gmail.com>
Date: Thu, 17 Jun 2010 09:46:30 -0700
Message-ID: <AANLkTikR7XZjvjnemKTnqzZOL2iweVUtmx5abSYgn...@mail.gmail.com>
Subject: Re: plparrot/perl6
To: plparrot@googlegroups.com
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Howdy,

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?

Thanks!

PS: Also, the output of "uname -a" would be useful too.

Duke



On Thu, Jun 17, 2010 at 12:39 AM, Hitoshi Harada <umi.tan...@gmail.com> wro=
te:
> 2010/6/16 Jonathan Leto <jal...@gmail.com>:
>> Howdy,
>>
>> 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
>
>
>
>> Duke
>>
>>
>>
>> On Sun, Jun 13, 2010 at 2:24 AM, Hitoshi Harada <umi.tan...@gmail.com> w=
rote:
>>> 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
>>> =91Parrot_str_new_constant=92
>>>
>>> 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.
>>>
>>> Regards,
>>>
>>> --
>>> Hitoshi Harada
>>>
>>
>>
>>
>> --
>> Jonathan "Duke" Leto
>> jonat...@leto.net
>> http://leto.net
>>
>
>
>
> --
> Hitoshi Harada
>



--=20
Jonathan "Duke" Leto
jonat...@leto.net
http://leto.net
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
