Something is probably segfaulting within your module's C code (or you've found a bug in Perl/XS). If all tests are passing, I guess the segfault would be happening rather late in the execution--maybe even right at cleanup.
To debug, by far the most efficient method would be to run it through an interactive debugger (or your preferred method of debugging segfaults) directly on a FreeBSD system.
Since you maintain several XS modules, my advice would be to grab an appropriate ISO of FreeBSD from http://www.freebsd.org/where.html and run it in a virtual machine, such as VirtualBox. Assuming average skill with basic OS installs, you can be debugging your module with standard development tools in under an hour.
If that option seems like too much work, you could try a web search for hosted FreeBSD shell accounts with development environments. I prefer the VM route, so I don't know of any I'd recommend off-hand.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||