Your message dated Sat, 3 May 2008 20:53:13 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#285532: vim: Regular expression "crash"
has caused the Debian Bug report #285532,
regarding [vim] Regular expression "crash"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
285532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285532
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: vim
Version: 1:6.3-013+2
Severity: normal
I was searching my ~/mbox for "315" (my area code) and after about 10
matches vim took a long time. I waited a few minutes and it still
had neither found the next match nore reported "search wrapped to
beginning". strace didn't say anything at all .. but gdb -p indicated
a stack smash ("previous frame inner to this frame"). I sent it a
kill (-15 I guess, the default) and it seemed to recover with a
message "crash detected, regular expression too complex?" or
something.
I'm not going to post my mailbox, but if I come up with a better
diagnosis, I'll report back.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (101, 'testing'), (99, 'unstable'), (9, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-rc1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages vim depends on:
ii dpkg 1.10.25 Package maintenance system for Deb
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libgpmg1 1.19.6-12.1 General Purpose Mouse Library [lib
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii vim-common 1:6.3-013+2 Vi IMproved - Common files
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Apr 04, 2006 at 01:21:46PM -0400, Justin Pryzby wrote:
> Did you read what this means? Line 58347 of my mailbox is 131344
> characters long!
Vim does have performance problems dealing with extremely long lines,
especially with highlighting for certain filetypes.
> It follows someones PGP sig, and is quite possibly
> not standards compliant (should be broken at 70 chars or so, no?). In
> fact I have no clue what it is .. other than a corrupted bzip file :),
> just that vim does not deal gracefully!
>
> This doesn't happen if I disable syntax highlighting.
Indeed, turning off syntax highlighting is usually one of the first
things to be suggested when dealing with large files or files which
contain long lines.
> Another old bug report referenced:
>
> http://greek0.net/~greek0/vim/bug1.html
>
> which seems to imply that one of the vim plugins (html) was working at
> O(n^2) WRT the line length; ouch!
That's specific to the HTML syntax highlighting, which isn't relevant
here.
As far as the initial "crash detected, regular expression too complex?"
message you got, I have been unable to reproduce that and am therefore
closing the bug.
I realize that the performance issues aren't ideal but there are known
workarounds as well as simply waiting for the search to complete.
Upstream also has some items on the todo list to try and improve
performance when dealing with such files.
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
--- End Message ---
