On Mon, Feb 20, 2012 at 10:10 PM, Lech Lorens <[email protected]> wrote: > On 20 February 2012 22:37, Bram Moolenaar <[email protected]> wrote: >> I can't reproduce it. If someone can, please use gdb to get a stack >> trace. >> > > Sending in a backtrace just in case: > > (gdb) bt > #0 0x0815b0a5 in update_screen (type=40) at screen.c:475 > #1 0x081e739a in main_loop (cmdwin=0, noexmode=0) at main.c:1185 > #2 0x081e6fcd in main (argc=3, argv=0xbffff0f4) at main.c:986
And just for good measure, my own one too: Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x00000000000000b8 0x000000010010fde3 in update_screen () (gdb) bt #0 0x000000010010fde3 in update_screen () #1 0x000000010018fd40 in main_loop () #2 0x0000000100193c72 in main () (I haven't compiled vim with the debugging symbols, but it may not be necessary now that we've confirmed it's in the same place across systems?) -- 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
