Re: [Nano-devel] [bug] segfault when pasting then cutting, when mark is on

[Benno Schulenberg]

Hi,

Revisiting this issue, getting a more interesting backtrace.

Open a new file, type a few <Enter>s, then:

first<Enter>
second<Cursor-up>
^K<Cursor-right>
Alt+A<Cursor-right>
^U^K

The cursor jumps to the top of the screen, second position.
Do a few <Cursor-right>s.  When you can't go any further
(the cursor is now on the first position of the second line),
do a <Cursor-up>.  The word "cond" appears.  If you now
try to go up or left... segmentation fault.

When the second ^K is done (the cursor is then on the first
position of a line that contains just "cond"), nano seemingly
cuts not from where the mark was set, but from the start
of the file...?


A slightly different scenario, with two extra <Cursor-right>s:

Open a new file, type a few <Enter>s, then:

first<Enter>
second<Cursor-up>
^K<Cursor-right><Cursor-right>
Alt+A<Cursor-right><Cursor-right>
^U^K

Segmentation fault, giving this backtrace:

#0  0x002896a7 in ?? () from /lib/tls/i686/cmov/libc.so.6
#1  0x0805bc40 in partition_filestruct (top=0x80da8b8, top_x=2, bot=0x80dc180, 
bot_x=0) at /usr/include/bits/string3.h:59
#2  0x0805beb5 in move_to_filestruct (file_top=0x8074404, file_bot=0x8074408, 
top=0x80da8b8, top_x=2, bot=0x80dc180, 
    bot_x=0) at nano.c:312
#3  0x0804e3ef in cut_marked () at cut.c:67
#4  0x0804e578 in do_cut_text (copy_text=false, cut_till_end=false, 
undoing=false) at cut.c:173
#5  0x0804e64e in do_cut_text_void () at cut.c:234
#6  0x0805c5e8 in do_input (meta_key=0xbffff38f, func_key=0xbffff38e, 
s_or_t=0xbffff38d, ran_func=0xbffff38c, 
    finished=0xbffff38b, allow_funcs=true) at nano.c:1667
#7  0x0805cfff in main (argc=1, argv=0xbffff454) at nano.c:2741

Anyone an idea where I should set breakpoints to get more useful information?

Benno

-- 
http://www.fastmail.fm - Access your email from home and the web