Hi Dominique,

On Thu, Mar 31, 2011 at 10:12 PM PDT, Dominique Pellé wrote:
DP> Mun wrote:
DP> 
DP> > Hi,
DP> >
DP> > My OS: Red Hat Enterprise Linux 5.6
DP> > My configure command:
DP> >   configure --with-features=huge --enable-perlinterp 
--enable-pythoninterp --enable-gui
DP> >
DP> > I must apologize that I don't have too much to go on with this issue,
DP> > but I'll provide what I have and I will try to get more data if requested.
DP> >
DP> > I had a simple macro that would take a line and reformat it by adding
DP> > strings to the beginning and ending of the line.  Nothing tricky or
DP> > complex.
DP> >
DP> > The file I was operating on had roughly 11,000 lines.  If I executed the
DP> > macro with a count of about 2,000 vim crashes on me.
DP> >
DP> > When I use the following vim command:
DP> > % vim --noplugin <filename>
DP> >
DP> > I get the following lines outut to the terminal when vim crashes:
DP> >
DP> > ------------------------------ Delimiter BEGIN 
--------------------------------
DP> >
DP> > BadRequest (invalid request code or no such operation)
DP> > Vim: Got X error
DP> > Vim: preserving files...
DP> > Vim: Finished.
DP> > 44;0MBadRequest (invalid request code or no such operation)
DP> > Vim: Got X error
DP> > Vim: Finished.
DP> > 44;0M
DP> > ------------------------------- Delimiter END 
---------------------------------
DP> 
DP> Hi
DP> 
DP> Things worth trying for debugging:
DP> 
DP> - put a breakpoint in x_error_handler(...) in vim/src/os_unix.c.
DP>   That's the function which prints "Vim: Got X error".  And
DP>   send the stack trace when it gets there.  Alternatively,
DP>   you can put an abort() in that function.  Vim will dump
DP>   core when the function is called and with gdb you can
DP>   look at the stack and variables.
DP> 
DP> - try running with valgrind memory checker.  It will run much
DP>   slower but it may catch something:
DP>   $ valgrind vim --log-file=valgrind.log
DP>   For more details, see: http://dominique.pelle.free.fr/valgrind.txt.html
DP> 
DP> In both cases, compile Vim with "CFLAGS = -g -O0" and
DP> make sure Vim is not stripped.  You can comment this
DP> line in src/Makefile:
DP> 
DP>    $(STRIP) $(DEST_BIN)/$(VIMTARGET)

Thanks for the excellent debug tips!  I'll try to get some additional
data in the coming days.

Regards,

-- 
Mun

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