Re: Does viminfo store nested lists?
Christian Brabandt
> Have you tried cyclic linked lists/ dictionaries like these samples ?
>
> fun! CyclicDictionary(count)
> let start = {}
> let prev = start
> for i in range(1, a:count)
> let new_ = {'prev': prev}
> endfor
> let start.prev = new_
>
> return start
> endf
>
>
> fun! CyclicList(count)
> let lists = map(range(0,a:count-1), '[]')
>
> for i in range(0, a:count-1)
> call add(lists[i], lists[(i+1) % a:count])
> call add(lists[i], lists[(i-1+a:count) % a:count])
> endfor
> return lists[0]
> endf
>
> let dict = CyclicDictionary(100000)
> let list = CyclicList(100000)
>
> if dict and list are both read back correctly neither size nor cycles
> seem to be a problem ..
Oh wow, simply sourcing that in my Windows gvim (7.4.0) crashes it.
(don't have a Windows development system here to analyze it or even
create a patch. Perhaps someone else can find the problem).
Best,
Christian
Ben Fritz
python and perl). But it is strange. I source the script and everything
seems fine. I can enter and exit insert mode without problem. About 30
seconds later, Vim crashes (when I'm not actually doing anything in
Vim).
This is gvim 32-bit running on 64-bit Windows 7.
Nikolay Pavlov
Does :call garbagecollect(1) trigger the crash?
>
> This is gvim 32-bit running on 64-bit Windows 7.
>
> --
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
Ben Fritz
immediately instead of after a long delay, when sourcing.
John Little
vim 7.4 from the Kubuntu repository does not, even with :call garbagecollect()
I'll make a debug build...
Regards, John Little
John Little
> I'll make a debug build...
Here's the last 12 lines of the backtrace:
#174623 0x0000000000461591 in set_ref_in_item (tv=0x3945220, copyID=2)
at eval.c:6974
#174624 0x00000000004614d9 in set_ref_in_list (l=0x2b89410, copyID=2)
at eval.c:6942
#174625 0x0000000000461591 in set_ref_in_item (tv=0x2b9f040, copyID=2)
at eval.c:6974
#174626 0x00000000004614d9 in set_ref_in_list (l=0x2b893b0, copyID=2)
at eval.c:6942
#174627 0x0000000000461591 in set_ref_in_item (tv=0x26adc00, copyID=2)
at eval.c:6974
#174628 0x000000000046149b in set_ref_in_ht (ht=0x8bb470 <globvardict+16>,
copyID=2) at eval.c:6927
#174629 0x000000000046126a in garbage_collect () at eval.c:6805
#174630 0x00000000004cb51f in vgetc () at getchar.c:1562
#174631 0x00000000004cbaf6 in safe_vgetc () at getchar.c:1795
#174632 0x000000000051bb67 in normal_cmd (oap=0x7fff19a758c0, toplevel=1)
at normal.c:666
#174633 0x0000000000620b5c in main_loop (cmdwin=0, noexmode=0) at main.c:1329
#174634 0x0000000000620468 in main (argc=1, argv=0x7fff19a75bc8) at main.c:1020
Never had a backtrace 174,634 levels deep before.
HTH, and regards, John Little
Bram Moolenaar
levels deep. Yep, valgrind confirms:
==20355== Stack overflow in thread 1: can't grow stack to 0xbe387fec
The solution would be to make this iterative instead of recursive.
Not so easy to do.
--
The users that I support would double-click on a landmine to find out
what happens. -- A system administrator
/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
Adrien Piérard
before making it iterative, one can try to make use of tail call
optimisation (using GOTO for loops if need be), or trampolines so as
to keep a constant stack.
P!
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
Français, English, 日本語, 한국어
John Little
> It appears to run out of stack space. Not strange when going 100000
> levels deep.
Indeed.
>The solution would be to make this iterative instead of recursive.
>Not so easy to do.
Indeed, I wasn't game to try. Be nice if it failed more gracefully, but other than imposing an arbitrary limit on the depth of a structure I can't think how. Even that would not be simple.
Regards, John