On Sun, Feb 8, 2009 at 1:11 AM, Mike Frysinger
<address@hidden> wrote:
seems to be related to syntax highlighting. when i have C highlighting turned
on, it's much more crashy.
try this (with highlighting and such turned on):
- run `nano foo.c`
- type: /**/
- hit home (to go to start of line)
- hit meta+t (to cut everything)
- hit ctrl+u (to paste everything)
- hit backspace
some garbage shows up. my guess is memory corruption. that's why sometimes
it "just works" for me and other times it segfaults and other times i get
garbage chars.
i would also look at the test case i posted in the last thread where you
posted a pre release
-mike
I'll do even better, run nano <file that doesnt exist>.c and type any character and it crashes.