sorry for the noise. it's fixed in 7.0-1.201 or it was a building problem. On Sun, 25 Mar 2007 14:59:52 +0200 Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> > Pancake wrote: > > > I've found a bug in vim, i have no time for debugging, but here's > > an example and a minor backtrace: > > > > looks like %edx is used as a pointer and this pointer is NULL. No > > idea if this should be fixed in this way, but here's some info: > > > > [EMAIL PROTECTED] vim -r /tmp/ > > Vim: Caught deadly signal SEGV > > > > Press ENTER or type command to continueVim: Finished. > > > > Segmentation fault > > > > 0x080e86d4 in ml_recover () > > (gdb) bt > > #0 0x080e86d4 in ml_recover () > > #1 0x080ddc38 in main () > > > > 0x080e86cc <ml_recover+284>: mov $0x1,%bl > > 0x080e86ce <ml_recover+286>: mov 0xfffffeec(%ebp),%edx > > 0x080e86d4 <ml_recover+292>: mov 0xc(%edx),%eax <---------here > > 0x080e86d7 <ml_recover+295>: mov %eax,(%esp) > > 0x080e86da <ml_recover+298>: call 0x80fe440 <vim_free> > > 0x080e86df <ml_recover+303>: mov 0xfffffeec(%ebp),%ecx > > 0x080e86e5 <ml_recover+309>: mov %ecx,(%esp) > > 0x080e86e8 <ml_recover+312>: call 0x80fe440 <vim_free> > > > > (gdb) info registers > > What is the source code? Compile for debugging. > > What version of Vim? Perhaps it's already fixed. > > What is your name? I don't like talking to a black box. > > -- > BRIDGEKEEPER: What is the air-speed velocity of an unladen swallow? > ARTHUR: What do you mean? An African or European swallow? > BRIDGEKEEPER: Er ... I don't know that ... Aaaaarrrrrrggghhh! > BRIDGEKEEPER is cast into the gorge. > "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD > > /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ > /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > \\\ download, build and distribute -- http://www.A-A-P.org /// > \\\ help me help AIDS victims -- http://ICCF-Holland.org /// > --pancake
