Thanks to all who've responded.
Yes, I have several VirtualBox VMs at hand for debugging cases like this, including a couple of different FreeBSDs. I just wasn't sure where to start, since simply running gdb didn't tell me much. I also could not duplicate the problem until I tried the Perl installed via ports. ikegami's tip to compile Perl with debugging on was helpful. I was able to see that the segfault is always happening during global clean up, after all my C/XS objects have been properly freed.
I've traced the problem to the MYMALLOC compile-time option. It only happens when that is on, which it is by default in FreeBSD ports Perl. So I'm now exploring that feature to see why it might be causing the issue.
More when I know it...
In reply to Re: Test::More wait status non-zero but all tests pass
by karpet
in thread Test::More wait status non-zero but all tests pass
by karpet
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |