> I would have to attribute the fact that it now runs unmodified on > FreeBSD to changes made elsewhere in the source code, but that is > largely conjecture. Is it possible that at this point only Linux is > affected?
Whether or not the segfault happens, the code was faulty. It was trampling a byte it shouldn't have. It'd be nice to know why the segfault didn't happen on FBSD... I suspect it's an uncaught error. It's very possible that some differences in the memory allocator allowed for such an access to not cause a segfault (trampling either another malloc()'s area, or trampling a "canary" or some slop appended to the mallocated memory. > No one has chimed in that it has failed on a non-Linux box. > I am not a programmer, and I don't have the skills to determine if the > problem lies in the Linux kernel. Is it possible other OSs may handle > the exception in a more graceful manner? Maybe a kernel geek could tell. It's most likely not a kernel issue, could be some differences in the libc and/or the interaction between it and the way perl is built on FBSD. Keep in mind that FreeBSD is more than just a different kernel... its userspace libc and the whole kit are built differently. I'd expect the answer lies in the way userspace memory allocations are done. =R= ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Razor-users mailing list Razor-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/razor-users
