Mun wrote:

> Hi,
>
> My OS: Red Hat Enterprise Linux 5.6
> My configure command:
>   configure --with-features=huge --enable-perlinterp --enable-pythoninterp 
> --enable-gui
>
> I must apologize that I don't have too much to go on with this issue,
> but I'll provide what I have and I will try to get more data if requested.
>
> I had a simple macro that would take a line and reformat it by adding
> strings to the beginning and ending of the line.  Nothing tricky or
> complex.
>
> The file I was operating on had roughly 11,000 lines.  If I executed the
> macro with a count of about 2,000 vim crashes on me.
>
> When I use the following vim command:
> % vim --noplugin <filename>
>
> I get the following lines outut to the terminal when vim crashes:
>
> ------------------------------ Delimiter BEGIN 
> --------------------------------
>
> BadRequest (invalid request code or no such operation)
> Vim: Got X error
> Vim: preserving files...
> Vim: Finished.
> 44;0MBadRequest (invalid request code or no such operation)
> Vim: Got X error
> Vim: Finished.
> 44;0M
> ------------------------------- Delimiter END 
> ---------------------------------

Hi

Things worth trying for debugging:

- put a breakpoint in x_error_handler(...) in vim/src/os_unix.c.
  That's the function which prints "Vim: Got X error".  And
  send the stack trace when it gets there.  Alternatively,
  you can put an abort() in that function.  Vim will dump
  core when the function is called and with gdb you can
  look at the stack and variables.

- try running with valgrind memory checker.  It will run much
  slower but it may catch something:
  $ valgrind vim --log-file=valgrind.log
  For more details, see: http://dominique.pelle.free.fr/valgrind.txt.html

In both cases, compile Vim with "CFLAGS = -g -O0" and
make sure Vim is not stripped.  You can comment this
line in src/Makefile:

   $(STRIP) $(DEST_BIN)/$(VIMTARGET)

Regards
-- Dominique

-- 
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

Raspunde prin e-mail lui