On Sun, July 7, 2013 18:03, meino.cra...@gmx.de wrote: > Loaded symbols for /lib64/libnss_files.so.2 > 0x00007f6140ef1f20 in ?? () from /usr/lib64/liblua.so.5 > (gdb) backtrace > #0 0x00007f6140ef1f20 in ?? () from /usr/lib64/liblua.so.5 > #1 0x00007f6140ee7fed in ?? () from /usr/lib64/liblua.so.5 > #2 0x00007f6140ef22b6 in ?? () from /usr/lib64/liblua.so.5 > #3 0x00007f6140ee7fed in ?? () from /usr/lib64/liblua.so.5 > #4 0x00007f6140ee72b7 in ?? () from /usr/lib64/liblua.so.5 > #5 0x00007f6140ee817e in ?? () from /usr/lib64/liblua.so.5 > #6 0x00007f6140ee3ea6 in lua_pcall () from /usr/lib64/liblua.so.5 > #7 0x00000000005930a8 in ?? () > #8 0x000000000046e584 in ?? () > #9 0x0000000000445e71 in ?? () > #10 0x00000000004469a5 in ?? () > #11 0x000000000044a832 in ?? () > #12 0x0000000000449292 in ?? () > #13 0x00000000004494c4 in ?? () > #14 0x0000000000449721 in ?? () > #15 0x000000000044a286 in ?? () > #16 0x000000000044a426 in ?? () > #17 0x000000000044a950 in ?? () > #18 0x000000000044ab99 in ?? () > #19 0x000000000048d3b6 in ?? () > #20 0x000000000048fb10 in ?? () > #21 0x000000000048fd1f in ?? () > #22 0x0000000000490b1b in ?? () > #23 0x00000000004cdaae in ?? () > #24 0x00000000004cdcf5 in ?? () > #25 0x0000000000462565 in ?? () > #26 0x000000000046e584 in ?? () > #27 0x0000000000445e71 in ?? () > #28 0x00000000004469a5 in ?? () > #29 0x000000000044a832 in ?? () > #30 0x000000000044e13b in ?? () > #31 0x000000000046e584 in ?? () > #32 0x000000000048323d in ?? () > #33 0x000000000048363a in ?? () > #34 0x00000000004150f5 in ?? () > #35 0x00007f6140b4f4cc in __libc_start_main () from /lib64/libc.so.6 > #36 0x0000000000417205 in ?? () > #37 0x00007fff813a1e58 in ?? () > #38 0x000000000000001c in ?? () > #39 0x0000000000000002 in ?? () > #40 0x00007fff813a263f in ?? () > #41 0x00007fff813a2643 in ?? () > #42 0x0000000000000000 in ?? ()
This stacktrace isn't really helpful. Please use a debug built of Vim (non-stripped). > > > ...the liblua-entries seems to indicate call to the lua-interpreter. > > The longest line of the dbfile is 71 characters long. So I think, at > least this is no problem ;) > > It seems to be a problem with one of the plugins. > Lua itsself read/interprets the dbfile without a second of delay, > though. > > I am not very motivated to step through all of my plugins switch them > off/on one by one... :-/ Well then we might not be able to fix this bug ;( Do you have any suspicious lua plugin? Try disabling this first and see if this helps. Also see the faq: http://vimhelp.appspot.com/vim_faq.txt.html#faq-36.12 You probably also want to have a look at profiling (:h profile) and verbose logging (:h -V). regards, Christian -- -- You received this message from the "vim_use" 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_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
