On Nov 6, 2007 3:24 AM, Thomas Dickey <[EMAIL PROTECTED]> wrote: > On Sun, Nov 04, 2007 at 11:00:18AM +0100, Heikki Hokkanen wrote: > > xterm seems to crash when doubleclicking on some lines (not all). > > I'm not sure where to look. I added that setting to my app-defaults, > and tried double-clicking around - no crash, and valgrind's not showing > me anything hidden. Perhaps it's some boundary case (such as line-wrapping > or scrollback) that isn't obvious.
It may be related to locale/umlauts somehow, but I'll leave the closer analysis to someone more knowledgeable. These crashes are triggered with the default locale (POSIX). I did plenty of testing with an IRC line that I noticed triggers the crash. Basically I shortened/modified it until selecting it stopped crashing xterm and then went back and figured a way to change it that would still end up in a crash. Here are some example lines that trigger the crash for me: 21:23:09 < _____> ____ä _______ä ___ ________ ____ä ___ä 21:23:09 > ____ä _______ä ___ ________ ____ä ___ä > ____ä _______ä ___ ________ ____ä ___ä ____ä _______ä ___ ________ ____ä ___ä _ä ___ ________ ____ä ___ä ____ä ___ä ____ö ___ö so looks like the line requires an "ouml" or "auml" to trigger the crash. Line length has possibly also got something to do with it. I don't know whether a space is needed though. Some example outputs on crash: Segmentation fault *** glibc detected *** xterm: free(): invalid next size (fast): 0x080d6710 *** *** glibc detected *** xterm: malloc(): memory corruption: 0x080d02d0 *** *** glibc detected *** xterm: free(): invalid next size (normal): 0x080d8338 *** Regards, -- Heikki Hokkanen
