vi.c coredump
walter harms
wharms at bfs.de
Thu Jun 19 13:49:03 UTC 2008
hi list,
i can produce a nasty bug in vi.
I noticed it first with 10.3 but it seems to be present in earlier versions.
I can produce the bug this way:
start vi
goto insert mode
select a screenfull of data with Xcursor
clip data into vi
<crash>
Your mileage may vary; picking only a few data will cause no harm.
btw: it is very unlikely that the problem is related to the compiler
since it happens on my desktop and in the embedded (non x86) system.
The following crash is with snapshot busybox-2008-03-04
Program received signal SIGSEGV, Segmentation fault.
0x08052895 in prev_line (p=0x0) at vi.c:1308
1308 if (p[-1] == '\n' && p > text)
re,
wh
ps: the .config is attached
pps: i have reported the bug early because i guess that the c&p approach may be used
by more people.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: _config
Url: http://lists.busybox.net/pipermail/busybox/attachments/20080619/58673bba/attachment.diff
More information about the busybox
mailing list