Loading ...
Sorry, an error occurred while loading the content.
 

crashing gvim

Expand Messages
  • Markus Fischer
    I disvovered a reproducable crash in Carbon gvim. %s/^M/ r/g on a file with one very long line(over 1000000 chars in this specific case) containing ^M
    Message 1 of 4 , Feb 27, 2003
      I disvovered a reproducable crash in Carbon gvim.
      %s/^M/\r/g on a file with one very long line(over 1000000 chars in this
      specific case)
      containing ^M linebreaks crashes vim with the
      following message(while started with -g from terminal):

      -------------------------
      Vim: Caught deadly signal
      Vim: preserving files...
      Vim: Finished.
      -------------------------


      the ~/Library/Logs/CrashReporter/Vim.crash.log:

      <snip>
      **********

      Date/Time: 2003-02-27 13:04:55 +0100
      OS Version: 10.2.4 (Build 6I32)
      Host: Lisa.local.

      Command: Vim
      PID: 791

      Exception: EXC_BAD_ACCESS (0x0001)
      Codes: KERN_INVALID_ADDRESS (0x0001) at 0x01a16075

      Thread 0 Crashed:
      #0 0x000d74f8 in syn_current_attr
      #1 0x000d7344 in syn_finish_line
      #2 0x000d5968 in syntax_start
      #3 0x000c63cc in win_line
      #4 0x000c5074 in win_update
      #5 0x000c3a3c in update_screen
      #6 0x0006b32c in main_loop
      #7 0x0006b040 in main
      #8 0x0000262c in _start (crt.c:267)
      #9 0x000024ac in start

      PPC Thread State:
      srr0: 0x000d74f8 srr1: 0x0200d930 vrsave: 0x00000000
      xer: 0x00000000 lr: 0x000d74e0 ctr: 0x90000e20 mq: 0x00000000
      r0: 0x00000000 r1: 0xbffff380 r2: 0x24022280 r3: 0x01a15fe8
      r4: 0x01585e90 r5: 0x00127000 r6: 0x00000000 r7: 0x00001000
      r8: 0x00073b14 r9: 0x018ef000 r10: 0x01a15fe8 r11: 0x0000008d
      r12: 0x24022280 r13: 0x00000000 r14: 0x00000000 r15: 0x00000e8b
      r16: 0x00000000 r17: 0x0010bd1c r18: 0xffffffff r19: 0x001158a4
      r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x001174c4
      r24: 0x00000000 r25: 0x0011243c r26: 0x00112448 r27: 0x00117d30
      r28: 0x00000000 r29: 0x0018dc50 r30: 0x01a15fe8 r31: 0x000d74c4

      </snap>



      my vim version is the latest official binary (6.1.320)




      Mit freundlichem Gruss

      Markus Fischer <fischer@...>
      --
      ---------------------------------------------------------------------
      MSNET phone +49 234 90200
      Dorstener Str. 347 fax +49 234 9020222
      D-44809 Bochum-Germany mailto:fischer@...
    • Benji Fisher
      ... [snip] ... [snip] It looks like Vim ran out of memory (on the stack, maybe) and that the syntax routines were involved. What was the file type? (I am
      Message 2 of 4 , Feb 27, 2003
        Markus Fischer wrote:
        > I disvovered a reproducable crash in Carbon gvim.
        > %s/^M/\r/g on a file with one very long line(over 1000000 chars in this
        > specific case)
        > containing ^M linebreaks crashes vim with the
        > following message(while started with -g from terminal):
        >
        > -------------------------
        > Vim: Caught deadly signal
        > Vim: preserving files...
        > Vim: Finished.
        > -------------------------
        >
        >
        > the ~/Library/Logs/CrashReporter/Vim.crash.log:
        [snip]
        >
        > Exception: EXC_BAD_ACCESS (0x0001)
        > Codes: KERN_INVALID_ADDRESS (0x0001) at 0x01a16075
        >
        > Thread 0 Crashed:
        > #0 0x000d74f8 in syn_current_attr
        > #1 0x000d7344 in syn_finish_line
        > #2 0x000d5968 in syntax_start
        [snip]

        It looks like Vim ran out of memory (on the stack, maybe) and that the
        syntax routines were involved. What was the file type? (I am trying to
        reproduce the problem, but I am running out of patience. I tried both
        100000a0123456789<C-V><C-M><Esc> and a0123456789<C-V><C-M><Esc>yy99999p:%j! and
        both methods take a long time...)

        > my vim version is the latest official binary (6.1.320)

        Not quite the latest: I posted 6.1.358 a couple of days ago...

        --Benji Fisher
      • Markus Fischer
        ... it was an sql file ... ah, seems to be fixed in that version. I tried the same file and it worked fine.
        Message 3 of 4 , Feb 27, 2003
          Am Donnerstag, 27.02.03 um 15:10 Uhr schrieb Benji Fisher:



          > It looks like Vim ran out of memory (on the stack, maybe) and
          > that the syntax routines were involved. What was the file type?

          it was an sql file

          > (I am trying to reproduce the problem, but I am running out of
          > patience. I tried both 100000a0123456789<C-V><C-M><Esc> and
          > a0123456789<C-V><C-M><Esc>yy99999p:%j! and both methods take a long
          > time...)
          >
          >> my vim version is the latest official binary (6.1.320)
          >
          > Not quite the latest: I posted 6.1.358 a couple of days ago...

          ah, seems to be fixed in that version.
          I tried the same file and it worked fine.
        • Benji Fisher
          ... I figured out how to make the file: make a line 0123456789 , then yy9p then :%j! and repeat the last two steps until you have a million
          Message 4 of 4 , Feb 27, 2003
            Markus Fischer wrote:
            >
            > Am Donnerstag, 27.02.03 um 15:10 Uhr schrieb Benji Fisher:
            >
            >
            >
            >> It looks like Vim ran out of memory (on the stack, maybe) and
            >> that the syntax routines were involved. What was the file type?
            >
            >
            > it was an sql file
            >
            >> (I am trying to reproduce the problem, but I am running out of
            >> patience. I tried both 100000a0123456789<C-V><C-M><Esc> and
            >> a0123456789<C-V><C-M><Esc>yy99999p:%j! and both methods take a long
            >> time...)

            I figured out how to make the file: make a line "0123456789<C-M>", then
            "yy9p" then ":%j!" and repeat the last two steps until you have a million
            characters. Then, try the substitution and listen to the hard disk go
            chugga-chugga. (no crash, though.)

            >>> my vim version is the latest official binary (6.1.320)
            >>
            >> Not quite the latest: I posted 6.1.358 a couple of days ago...
            >
            > ah, seems to be fixed in that version.
            > I tried the same file and it worked fine.

            I may be wrong, but I suspect it has more to do with the status of your
            memory than with the version of vim. Either way, it does not sound Mac-specific.

            --Benji Fisher
          Your message has been successfully submitted and would be delivered to recipients shortly.