[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 255800] New: "find in files" for a string ending in an LF
From:       Diggory Hardy <diggory.hardy () gmail ! com>
Date:       2010-11-01 11:15:42
Message-ID: bug-255800-40295 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=255800

           Summary: "find in files" for a string ending in an LF character
                    matches all lines, potentially resulting in bad
                    performance.
           Product: kdevelop
           Version: 4.0.1
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs@kdevelop.org
        ReportedBy: diggory.hardy@gmail.com


Version:           4.0.1 (using KDE 4.4.5) 
OS:                Linux

As subject line/below.

I'm not entirely sure if bad argument passing to xargs or an external bug is to
blame, but a symptom of this is that the "find in files" result window can
easily be filled with huge volumes of output making kdevelop respond very
poorly (possibly just while the output is being copied to this frame; not
sure). Thus it would be a good idea additionally to have a restriction on the
amount of content that this frame can take or a warning with an option to abort
when too much content is injected (can't give much info on a sensible limit,
sorry).

Reproducible: Always

Steps to Reproduce:
Search in all files for any string ending with an LF (0x0A) character (warning:
I'd advise picking a directory to search in containing only a few files to
avoid the responsiveness issues described above).

Actual Results:  
All lines of all files are found, resulting in a lot of output and poor
performance of kdevelop.

Expected Results:  
Some kind of catch to prevent such unresponsive behaviour, and either for the
bad (multiline) regular expression to result in an error message rather than
incorrect matches or for it to match across lines properly.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]