Britton Kerin wrote:
> The node currently reads like this:
>
> When Vim crashes in one of the test files, and you are using gcc for
> compilation, here is what you can do to find out exactly where Vim crashes.
> This also applies when using the MingW tools.
>
> 1. Compile Vim with the "-g" option (there is a line in the Makefile for this,
> which you can uncomment).
>
> 2. Execute these commands (replace "11" with the test that fails): >
> cd testdir
> gdb ../vim
> run -u unix.vim -U NONE -s dotest.in test11.in
>
> ...
>
> The first problem is that there doesn't seem to be a line in the
> Makefile for adding the -g option. I don't think its needed really, as
> it seems that the -g option gets used anyway.
This is different for every compiler and it depends on your environment.
Searching in Makefile for "-g\>" leads you to the right spot, with
comments.
> The next problem is that the binaries get stripped at installation time,
> and the docs don't mention this. It works if you use the constructed
> binary in place but not otherwise.
That's why it says to Compile Vim and use "gdb ../vim".
--
Give a man a computer program and you give him a headache,
but teach him to program computers and you give him the power
to create headaches for others for the rest of his life...
R. B. Forest
/// Bram Moolenaar -- [email protected] -- 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 ///
--
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
