Skip Menu |

This queue is for tickets about the IPC-ShareLite CPAN distribution.

Report information
The Basics
Id: 29793
Status: resolved
Priority: 0/
Queue: IPC-ShareLite

People
Owner: Nobody in particular
Requestors: steve [...] mouf.net
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: test failure with perl's internal malloc
Date: Fri, 5 Oct 2007 09:37:07 -0400
To: bug-IPC-ShareLite [...] rt.cpan.org
From: Steve Wills <steve [...] mouf.net>
IPC::ShareLite's test cases fail when using a perl that is compiled to use it's own internal malloc instead of the system malloc. A perl that uses it's own malloc can be identified by running perl - V:usemymalloc. If the internal malloc is in use, it will return "usemymalloc='y';". If not, it will return "usemymalloc='n';". I don't have the output of the make test to demonstrate any more, but it fails on test case 4 and causes a signal 11 (seg fault) and core dump on the final test case. I believe this may be due to a bug in IPC::ShareLite that isn't exposed by other mallocs.
On Fri Oct 05 09:37:45 2007, steve@mouf.net wrote: Show quoted text
> IPC::ShareLite's test cases fail when using a perl that is compiled > to use it's own internal malloc instead of the system malloc. A perl > that uses it's own malloc can be identified by running perl - > V:usemymalloc. If the internal malloc is in use, it will return > "usemymalloc='y';". If not, it will return "usemymalloc='n';". I > don't have the output of the make test to demonstrate any more, but > it fails on test case 4 and causes a signal 11 (seg fault) and core > dump on the final test case. I believe this may be due to a bug in > IPC::ShareLite that isn't exposed by other mallocs.
This is fixed in 0.10. Thanks for the report.