It looks like everything is getting double-freed. Try exiting the
threads with POSIX::_exit(). That'll prevent all cleanup code from
being run.
The consequences of doing that may be dire (massive memory-leak, among
others), but I'm curious about the results for you.
PerlQt is highly allergic to ithreads. The code assumes there is a 1:1
relationship between Qt objects and Perl objects, and when ithreads
clones the interpreter, hell breaks loose.
Cheers,
Ashley Winters
--- Gary Greene <greeneg@xxxxxxxxxxxxx> wrote:
> Not precisely a perlqt issue, but perl related. I'm trying to move
> the
> system( rpm ) calls into threads and am having trouble getting it to
> not
> SigSegv. The code is attached and the output from the terminal is
> also
> attached.
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
|
