Hi Ben, Thanks for your reply. Please see my comments below.
On Thu, Mar 31, 2011 at 03:24 PM PDT, Ben Schmidt wrote: BS> On 31/03/11 3:51 PM, Mun wrote: BS> >Hi, BS> > BS> >My OS: Red Hat Enterprise Linux 5.6 BS> >My configure command: BS> > configure --with-features=huge --enable-perlinterp --enable-pythoninterp --enable-gui BS> > BS> >I must apologize that I don't have too much to go on with this issue, BS> >but I'll provide what I have and I will try to get more data if requested. BS> BS> Obviously Vim's reporting something related to X. Were you using BS> Vim's GUI at the time, or just console Vim? GUI. BS> Did your macros make use of the system/X clipboard at all, or does BS> your 'guioptions' or 'clipboard' setting mean that it would have BS> been used for Vim's unnamed register? Here is my macro (with non-printable chars replaced by <> representations): 0yypkIforce <ESC>A.notifier1 = 1'b0;<ESC><CR>"aPA);<ESC><CR> Here is how I have guioptions set: guioptions=abceFgimrt To answer your question, I believe the answer is that my system/X clipboard would not be used in this scenario. BS> Just a couple more pieces of data that might be helpful, though I BS> have no idea what's going on. Good questions. If I have time, maybe I'll download the Motif development libs and try a compilation with Motif instead of GTK+ 2 . I'm just not sure if I want to have to deal with the font differences and stuff. Regards, -- Mun BS> Ben. BS> BS> BS> BS> >I had a simple macro that would take a line and reformat it by adding BS> >strings to the beginning and ending of the line. Nothing tricky or BS> >complex. BS> > BS> >The file I was operating on had roughly 11,000 lines. If I executed the BS> >macro with a count of about 2,000 vim crashes on me. BS> > BS> >When I use the following vim command: BS> >% vim --noplugin<filename> BS> > BS> >I get the following lines outut to the terminal when vim crashes: BS> > BS> >------------------------------ Delimiter BEGIN -------------------------------- BS> > BS> >BadRequest (invalid request code or no such operation) BS> >Vim: Got X error BS> >Vim: preserving files... BS> >Vim: Finished. BS> >44;0MBadRequest (invalid request code or no such operation) BS> >Vim: Got X error BS> >Vim: Finished. BS> >44;0M BS> >------------------------------- Delimiter END --------------------------------- BS> > BS> > BS> >And when I use the following vim command: BS> >% vim -u NONE -U NONE --noplugin<filename> BS> > BS> >My terminal window fills up with the following repeating lines: BS> > BS> >------------------------------ Delimiter BEGIN -------------------------------- BS> > BS> >Vim: Got X error BS> >BadRequest (invalid request code or no such operation) BS> >Vim: Got X error BS> >BadRequest (invalid request code or no such operation) BS> >Vim: Got X error BS> >BadRequest (invalid request code or no such operation) BS> >Vim: Got X error BS> >BadRequest (invalid request code or no such operation) BS> >Vim: Got X error BS> >BadRequest (invalid request code or no such operation) BS> >Vim: Got X error BS> >BadRequest (invalid request code or no such operation) BS> >Vim: Got X error BS> >Vim: Caught deadly signal SEGV BS> > BS> >------------------------------- Delimiter END --------------------------------- BS> > BS> > BS> >One last piece of data: I compiled the same vim source files on a Red BS> >Hat Enterprise Linux 4 system and used my same plugins and rc files and BS> >ran the same macro in the same way and it ran without issue; even with a BS> >count of 11,000 . BS> > BS> >See below for the complete :ver information from both systems. BS> > BS> >A core file wasn't written; thus, I can't provide a backtrace. BS> > BS> >Regards, BS> > BS> BS> -- BS> You received this message from the "vim_dev" maillist. BS> Do not top-post! Type your reply below the text you are replying to. BS> For more information, visit http://www.vim.org/maillist.php -- 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
