awshirley Wrote: > It died twice during a library scan. Nothing showed up on the screen > indicating an error message, just a segmentation fault.
It said 'segmentation fault'? That specific string is coming from the kernel when a process misbehaves itself and tries to get to memory it hasn't asked nicely for. Ie, a pointer points to '0xf9f89f99' or somesuch and the kernel, keeper of memory, knows that the application didn't ask for that. Now, in Perl, you can't do that. 'Real' pointers just aren't used by programmers: there is a layer of abstraction and you can't get past it that I know of. So that would imply a bug in Perl.... but Perl is very well-studied by lots of projects, and though it almost certainly will always have bugs, such bugs should be easy to reproduce, not rarities like yours. So what this sounds like to me is the classic, "when i try to build a new kernel, gcc segfaults!" problem, which isn't gcc or linux at all: it's almost always a bad memory simm. http://www.bitwizard.nl/sig11/ has more details on this. -- snarlydwarf _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
