Dominique Pellé wrote:
François Ingelrest wrote:
On 26 December 2013 17:54, Dominique Pellé wrote:
You need to:
- build vim with -g -O0
- make sure vim is not stripped (uncomment #STRIP = /bin/true
in vim/src/Makefile). Or run vim from the vim/src/. directory,
as it is not stripped there.
- start vim with gdb:
$ cd vim/src
$ gdb ./vim
(gdb) run
... and when it crashes...
(gdb) backtrace
Vim doesn't crash when compiled with -g -O0 so I don't get a stack
trace, although it's impossible to edit the buffer as Lech said.
$ cd vim/src
$ valgrind --log-file=valgrind.log \
--track-origins=yes \
--num-callers=50 ./vim
Attached is the Valgrind log.
Salut François
I still cannot reproduce the bug somehow. Maybe it depends
on some settings in your ~/.vimrc. Nevertheless, the error
you find with valgrind is useful: [snip]
Hello!
I'm using vim 7.4.131 (Huge version with GTK2-GNOME GUI), and haven't
used Dominque's patch. When trying your problem out, netrw went up a
directory, even though foo no longer existed; both going-up-directory
techniques worked (<return> on "..", and using "-").
I then tried using
vim -u simple.vimrc
where <simple.vimrc> contained the following two lines, only:
set nocp
filetype plugin on
Again, no problems. I don't think I can fix this problem thus far. Do
you have any netrw-associated settings that you could share?
Regards,
C Campbell
--
--
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
