GNOME Bugzilla – Bug 335977
gnome-search-tools crashes with regular expressions containing "[" as a caracter
Last modified: 2006-03-25 18:11:23 UTC
Steps to reproduce: 1. Open gnome-search-tools 2. Enter as regular expression to search : .*[.* or .*\[.* 3. Type enter Stack trace: Debugging Information: Backtrace was generated from '/usr/bin/gnome-search-tool' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223841568 (LWP 17901)] [New Thread -1227838544 (LWP 17903)] [New Thread -1227420752 (LWP 17902)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 67236
Thread 1 (Thread -1223841568 (LWP 17901))
Other information: It happens everytime on every directory .*].* or .*\].* works fine.
regcomp() considers .*[.* and .*\[.* invalid regular expression patterns. You can use .*[\[].* instead. I fixed the crasher. Thanks. Fixed in CVS (HEAD and 2-14 branches). 2006-03-25 Dennis Cranston <dennis_cranston@yahoo.com> * gsearchtool-support.c: (compare_regex): Fix bug #335977, crash with invalid regular expressions.