Opened 5 years ago

Last modified 3 years ago

#14693 new defect

Debian unstable Params::Classify perl module causes pidgin to crash

Reported by: guysoft Owned by: EionRobb
Milestone: Component: unclassified
Version: 2.10.0 Keywords:
Cc:

Description

Hey, After upgrading to version 2.10.0 Pidgin segfaults at startup. Attached is the stack trace.

Attachments (1)

pidgin-backtrace.log (9.9 KB) - added by guysoft 5 years ago.
Stack trace of the segfault

Download all attachments as: .zip

Change History (11)

Changed 5 years ago by guysoft

Stack trace of the segfault

comment:1 Changed 5 years ago by guysoft

  • Summary changed from cPidgin segfaults on debian unstable - issues with libperl.so.5.12 to Pidgin segfaults on debian unstable - issues with libperl.so.5.12

comment:2 follow-up: Changed 5 years ago by deryni

evilnebby in #pidgin reported this the other day as well.

He tracked it down to a plugin of his using the perl DateTime? module (both the normal and PP versions). I imagine other modules may trigger the same issue, though confirmation of that would be helpful.

He worked around the problem by using a run-time require of the module instead of a compile-time use of it.

Figuring out what exactly the problem here is would be great but I'm not sure how best to go about debugging it at the moment and don't have a machine on which to poke at it myself right now.

comment:3 in reply to: ↑ 2 Changed 5 years ago by guysoft

Replying to deryni:

evilnebby in #pidgin reported this the other day as well.

He worked around the problem by using a run-time require of the module instead of a compile-time use of it.

Could evilnebby the steps of what he did? So I can workaround this too?

Figuring out what exactly the problem here is would be great but I'm not sure how best to go about debugging it at the moment and don't have a machine on which to poke at it myself right now.

I can give you access to the box here if that would help you.

comment:4 Changed 5 years ago by guysoft

Ok, I found which plugin caused, the problem, but I have no idea why: https://github.com/guysoft/Twitter-Status/blob/master/twitter-status.pl Its a plugin i wrote that is based on the identica plugin. They both crash.

comment:5 Changed 5 years ago by guysoft

Ok, more research shows that this happens in every perl plugin. However it works fine if a I load a plain perl module without any external includes.

Is there a way to check the path and see if perl is finding the modules correctly?

comment:6 Changed 5 years ago by guysoft

  • Summary changed from Pidgin segfaults on debian unstable - issues with libperl.so.5.12 to Pidgin segfaults on debian unstable if enabling Perl-based modules - issues with libperl.so.5.12

comment:7 Changed 5 years ago by guysoft

I ran an strace and saw the segault happens right before loading Params::Classify perl module. Googling why it might cause such a segfault led me to find its not thread safe. So far thats the only lead I got to why this problem persists: http://www.perlmonks.org/index.pl?node_id=886909

comment:8 Changed 5 years ago by guysoft

  • Summary changed from Pidgin segfaults on debian unstable if enabling Perl-based modules - issues with libperl.so.5.12 to Debian unstable Params::Classify perl module causes pidgin to crash

comment:9 Changed 5 years ago by guysoft

I finally managed to workaround this issue. In order to do that I reinstalled about 50 modules from CPAN (also had to use this blog because Crypt::SSLeay does not compile on debian/ubuntu : https://colinnewell.wordpress.com/2011/10/24/cryptssleay-and-ubuntu-11-10/ )

I can clearly see the segfault happens on Params::Classify.

comment:10 Changed 3 years ago by rekkanoryo

  • Owner changed from rekkanoryo to EionRobb
Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!