On 17.07.2010 8:18, Mario Sergio Fujikawa Ferreira wrote:
> Hi,
>
> I am running 8-STABLE as of July 1st 2010.
>
> FreeBSD exxodus.fedaykin.here 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #14: Thu
> Jul 1 12:50:38 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64
>
> With lat
alled-back' by Configure
< # after it has prompted the user for whether to use threads.
---
> # This script UU/usethreads.cbu will get 'called-back' by Configure
> # after it has prompted the user for whether to use threads.
Scott
-Original Message-
From: Christopher Key [mai
On Tue, 20 Jul 2010 07:37:37 -0700
"Scott Sanbeg" wrote:
> The patch could possibly solve my challenge, but if it works then why do I
> get this?
>
> r...@anchorage:/usr/ports/lang/perl5.12# patch < my.patch
> Hmm... Looks like a unified diff to me...
> The text leading up to this was:
> --
Scott Sanbeg wrote:
> The patch could possibly solve my challenge, but if it works then why do I
> get this?
>
> r...@anchorage:/usr/ports/lang/perl5.12# patch < my.patch
> Hmm... Looks like a unified diff to me...
> The text leading up to this was:
> --
> |--- files/patch-
org
[mailto:owner-freebsd-po...@freebsd.org] On Behalf Of Christopher Key
Sent: Sunday, July 18, 2010 8:46 PM
To: po...@freebsd.org
Subject: Re: lang/perl5.12 segfault (amd64 - 8-STABLE)
cj...@cam.ac.uk wrote:
> Someone who understands the perl threading internals needs to figure
> this out.
>
On Mon, 19 Jul 2010, Christopher Key wrote:
Simple solution, there was a missing -lpthread, patch available from:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148648
Hehe... I completely overlooked this possibility. I sent a follow-up
to perl5-porters quoting your message.
For some reas
cj...@cam.ac.uk wrote:
> Someone who understands the perl threading internals needs to figure
> this out.
>
>
Simple solution, there was a missing -lpthread, patch available from:
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148648
For some reason, linking binaries without -lpthread succe
On Saturday, 2010-07-17 at 09:23:18 +, Janne Snabb wrote:
The problem seems to go away when threads are disabled.
The problem appears on i386 in addition to amd64, probably other
architectures as well.
My advice would be: DO NOT try to upgrade your perl to 5.12 if you
are using threads (w
On Saturday, 2010-07-17 at 09:23:18 +, Janne Snabb wrote:
> The problem seems to go away when threads are disabled.
> The problematic line 311 in util.c expands to quite a horrible mess
> (found this out by doing make util.i):
> (void)( { if ((PL_curinterp)) { PerlInterpreter* my_perl
> __a
On Sat, 17 Jul 2010, Janne Snabb wrote:
It is somehow related to the "Perl_debug_log" which is the first
argument of PerlIO_printf. But I can not figure out why, too many
layers of #defines and calls within calls.
The problem seems to go away when threads are disabled.
The problematic line 31
Hi,
Same problem here.
Here is the gdb output:
#0 0x004ddbd3 in Perl_safesyscalloc (count=1, size=4072) at util.c:311
311 DEBUG_m(PerlIO_printf(Perl_debug_log, "0x%"UVxf": (%05ld) calloc %ld x
%ld bytes\n",PTR2UV(ptr),(long)PL_an++,(long)count,(long)total_size));
(gdb) bt
#0
On 17.07.2010 06:18 (UTC+1), Mario Sergio Fujikawa Ferreira wrote:
Hi,
I am running 8-STABLE as of July 1st 2010.
FreeBSD exxodus.fedaykin.here 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #14: Thu
Jul 1 12:50:38 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64
With late
Hi,
I am running 8-STABLE as of July 1st 2010.
FreeBSD exxodus.fedaykin.here 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #14: Thu
Jul 1 12:50:38 BRT 2010 li...@exxodus:/usr/obj/usr/src/sys/LIOUX amd64
With latest ports as of July 14th 2010.
I've been trying to build per
13 matches
Mail list logo
