[rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2021-01-13 Thread Roderich Schupp via RT
Wed Jan 13 05:42:42 2021: Request 68892 was acted upon. Transaction: Correspondence added by RSCHUPP Queue: PAR-Packer Subject: perl-threads @ Linux => Segment fault Broken in: (no value) Severity: Important Owner: Nobody Requestors: p...@cpan.org Status: open Tic

Re: [rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-20 Thread Juan José 'Peco' San Martín via RT
Mon Jun 20 11:50:36 2011: Request 68892 was acted upon. Transaction: Correspondence added by jsanmar...@gmail.com Queue: PAR-Packer Subject: Re: [rt.cpan.org #68892] perl-threads @ Linux => Segment fault Broken in: (no value) Severity: Important Owner: Nobody Request

Re: [rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-20 Thread Juan José 'Peco' San Martín
Ok, first say that IMHO is not a bug about PAR. In case somebody can reproduce the behavior, maybe we could add a note somewhere for developers. I did some tests and...if a thread that calls another thread (to force the usage of the stack) loads a good amount of perl modules, then, in case we want

[rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-20 Thread Roderich Schupp via RT
Mon Jun 20 09:54:59 2011: Request 68892 was acted upon. Transaction: Correspondence added by RSCHUPP Queue: PAR-Packer Subject: perl-threads @ Linux => Segment fault Broken in: (no value) Severity: Important Owner: Nobody Requestors: p...@cpan.org Status: open Tic

Re: [rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-20 Thread Juan José 'Peco' San Martín via RT
Mon Jun 20 07:29:40 2011: Request 68892 was acted upon. Transaction: Correspondence added by jsanmar...@gmail.com Queue: PAR-Packer Subject: Re: [rt.cpan.org #68892] perl-threads @ Linux => Segment fault Broken in: (no value) Severity: Important Owner: Nobody Request

Re: [rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-20 Thread Juan José 'Peco' San Martín
You are right, I need time to show you an example (sorry the App is huge and it's not easy to strip it). Anyway, the issue is that the stack should be increased if you want to PAR it, and I don't understand why. Thanks Peco 2011/6/20 Roderich Schupp via RT > Mon Jun 20 07:05:17 2011: Request

[rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-20 Thread Roderich Schupp via RT
Mon Jun 20 07:05:17 2011: Request 68892 was acted upon. Transaction: Correspondence added by RSCHUPP Queue: PAR-Packer Subject: perl-threads @ Linux => Segment fault Broken in: (no value) Severity: Important Owner: Nobody Requestors: p...@cpan.org Status: open Tic

Re: [rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-20 Thread Juan José 'Peco' San Martín via RT
Mon Jun 20 06:33:40 2011: Request 68892 was acted upon. Transaction: Correspondence added by jsanmar...@gmail.com Queue: PAR Subject: Re: [rt.cpan.org #68892] perl-threads @ Linux => Segment fault Broken in: (no value) Severity: Important Owner: Nobody Requestors

Re: [rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-20 Thread Juan José 'Peco' San Martín
Hi I've been studying the issue, and here is my workaround. The program uses Threads, Threads::Shared, Tk and opens several sockets. It works fine as .pl although it uses the directive: threads->set_stack_size(3); in order to avoid a Segment Fault. If I PAR'ed' this program (pp program.pl -o

[rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-20 Thread Roderich Schupp via RT
Mon Jun 20 04:02:16 2011: Request 68892 was acted upon. Transaction: Correspondence added by RSCHUPP Queue: PAR Subject: perl-threads @ Linux => Segment fault Broken in: (no value) Severity: Important Owner: Nobody Requestors: p...@cpan.org Status: new Ticket http

[rt.cpan.org #68892] perl-threads @ Linux => Segment fault

2011-06-17 Thread Juan Jose San Martin via RT
Fri Jun 17 06:14:16 2011: Request 68892 was acted upon. Transaction: Ticket created by PECO Queue: PAR Subject: perl-threads @ Linux => Segment fault Broken in: (no value) Severity: Important Owner: Nobody Requestors: p...@cpan.org Status: new Ticket https://rt.cp