I did that .. and a regular Perl program runs fine. When I use the module, it goes crazy. Another development is that I cannot use the debugger now - when I run the program in the debugging mode, I do not get the debugger prompt. Instead, it hangs and I see that CPU utilization hits 100%. I have to forcibly stop and kill the process (Ctrl Z & kill -9 PID).
What's surprising is that other programs that use the same module are running fine. I'm not sure what's so special about this piece of code that's making Perl angry that it throws a "Memory fault" at me.
