briandfoy/crypt-rijndael — Issue #2: is this module thread safe?
Author: obilodeau
Created: 2012-02-07 17:07:03+00:00
State: open

I've seen a segfault in the perl vm on a multi-threaded daemon that uses Crypt::Rijndael (through Net::SNMP actually).

At this point I don't know for sure by what it's caused by I thought I would save some time by asking you if you knew if the module is thread safe or not since it's not explicitly documented.

Here's the stacktrace:
```
*** glibc detected *** /usr/bin/perl: double free or corruption (fasttop): 0x9e70bc38 ***
... one line omitted ...
======= Backtrace: =========
/lib/libc.so.6[0xa666c5]
/lib/libc.so.6(cfree+0x59)[0xa66b09]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_newCONSTSUB+0x154)[0x150354]
/usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/auto/Crypt/Rijndael/Rijndael.so(boot_Crypt_
_Rijndael+0x491)[0x9
ce201]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_pp_entersub+0x40d)[0x18952d]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_runops_standard+0x1f)[0x18299f]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so[0x12303e]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so(Perl_call_sv+0x5e6)[0x127906]
/usr/lib/perl5/5.8.8/i386-linux-thread-multi/auto/threads/threads.so(Perl_ithread_run+0x1ae)[0x968a5
e]
/lib/libpthread.so.0[0xba4832]
/lib/libc.so.6(clone+0x5e)[0xacf45e]
```

Thanks,
Big fan of your work btw.