Re: [HACKERS] plperl segfault in plperl_trusted_init() on kfreebsd

2013-05-21 Thread Christoph Berg
Re: Andrew Dunstan 2013-05-17 <51964770.6070...@dunslane.net> > I have reproduced this. It happens with both the distro perl and a > home-built perl 5.14. AFAICT this is a Perl bug. Any reference at > all to ERRSV at the point this occurs causes a core dump, even just > assigning it to a local SV *

Re: [HACKERS] plperl segfault in plperl_trusted_init() on kfreebsd

2013-05-17 Thread Andrew Dunstan
On 05/16/2013 09:14 AM, Christoph Berg wrote: Re: Stephen Frost 2013-05-16 <20130516123344.gt4...@tamriel.snowman.net> * Christoph Berg (c...@df7cb.de) wrote: That was because the plain "./configure" version (for a minimal way to reproduce) didn't built with debug symbols. The original gcc lin

Re: [HACKERS] plperl segfault in plperl_trusted_init() on kfreebsd

2013-05-16 Thread Stephen Frost
* Christoph Berg (c...@df7cb.de) wrote: > This wasn't the Debian build, but just plain "./configure --with-perl" > without any other arguments. As said in the previous mail, both this > and the Debian build segfault here. (Which means there is no -dbg > package because the build fails.) Oh, I see

Re: [HACKERS] plperl segfault in plperl_trusted_init() on kfreebsd

2013-05-16 Thread Christoph Berg
Re: Stephen Frost 2013-05-16 <20130516123344.gt4...@tamriel.snowman.net> > * Christoph Berg (c...@df7cb.de) wrote: > > That was because the plain "./configure" version (for a minimal way to > > reproduce) didn't built with debug symbols. The original gcc line from the > > Debian build log is: > >

Re: [HACKERS] plperl segfault in plperl_trusted_init() on kfreebsd

2013-05-16 Thread Stephen Frost
* Christoph Berg (c...@df7cb.de) wrote: > That was because the plain "./configure" version (for a minimal way to > reproduce) didn't built with debug symbols. The original gcc line from the > Debian build log is: It did, but Debian (and Ubuntu and friends) pull the debugging symbols out of the bin

Re: [HACKERS] plperl segfault in plperl_trusted_init() on kfreebsd

2013-05-15 Thread Christoph Berg
Re: Tom Lane 2013-05-15 <244.1368675...@sss.pgh.pa.us> > You sure that wholesale override of CFLAGS is a good idea? > This report doesn't show what flags the rest of your system was built > with, but seems like there could be a compatibility issue. Or maybe > you prevented plperl from being built

Re: [HACKERS] plperl segfault in plperl_trusted_init() on kfreebsd

2013-05-15 Thread Tom Lane
Christoph Berg writes: > Here's what I did: > ./configure > cd src && make > cd pl/plperl && make clean && make CFLAGS="-g" > make check You sure that wholesale override of CFLAGS is a good idea? This report doesn't show what flags the rest of your system was built with, but seems like there cou

[HACKERS] plperl segfault in plperl_trusted_init() on kfreebsd

2013-05-14 Thread Christoph Berg
The newly activated "make check-world" on Debian (I haven't found the time yet to follow up on the other threads I opened for that, sorry) actually found something: plperl and plperlu segfault on the kfreebsd-amd64 and kfreebsd-i386 architectures. These are FreeBSD 9 kernels with a GNU/Debian userl