Coming from a C background also, I'm also (too:) faliliar with this kind of trap from C-code.

If you re-read the symptoms I list. The trap is influnced by the presence of commented out code? That is to say, not only does adding a commented out print statement prevent the trap, but value of the arguments to that commented out print statement also influence whether the trap occurs?

Also note that the program only traps (whether the comment is present or not) when being profiled. In all other circumstances it runs flawlessly?