Re^2: debugging possible memory crash?

I would agree with cdarke. Possibly some non-ASCII characters (UTF-8?) are being output and your xterm cannot handle it -- but I haven't seen that in quite some time. What system are you running and what version of xterm do you have?

-derby

Comment on Re^2: debugging possible memory crash?

Replies are listed 'Best First'.
Re^3: debugging possible memory crash? by Anonymous Monk on Jun 11, 2007 at 14:56 UTC
Actually, I'm running aterm 0.4.2p1 on OpenBSD 4.1. Do you know how I would check to see if characters are UTF-8?	[reply]
Re^4: debugging possible memory crash? by cdarke (Prior) on Jun 11, 2007 at 15:29 UTC
Does aterm support UTF-8? I Googled your terminal type and it appears it is a colour vt102 emulator. Most terminal drivers only support ASCII, not even ISO Latin 1 let alone UTF-8. I suggest you add to your loop a write of the characters to a file just before you write to the screen. Make the file handle unbuffered in case it is crashing perl (although that is doubtful, it is worth the precaution). That way you should be able to track down which characters are causing the problem (and if indeed this is the cause) by looking at the output file after the "crash". I find od -xc a useful tool for this kind of issue.	[reply]