GNOME Bugzilla – Bug 357050
Crash replacing \n\n with \n or undoing after paste
Last modified: 2007-10-06 16:35:09 UTC
Version: 2.16.0 What were you doing when the application crashed? i ran search and replace \n\n to \n Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 47222784 vsize: 0 resident: 47222784 share: 0 rss: 23011328 rss_rlim: 0 CPU usage: start_time: 1158843299 rtime: 0 utime: 145 stime: 0 cutime:137 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226475120 (LWP 14196)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 72909
Thread 1 (Thread -1226475120 (LWP 14196))
*** Bug 357891 has been marked as a duplicate of this bug. ***
*** Bug 359235 has been marked as a duplicate of this bug. ***
*** Bug 359530 has been marked as a duplicate of this bug. ***
*** Bug 360167 has been marked as a duplicate of this bug. ***
Created attachment 74266 [details] The file is generated by OpenModelica. This file causes gedit to crash when the Find/replace operation are executed with "\n\n" as "find" and "\n" as "replace with".
*** Bug 366900 has been marked as a duplicate of this bug. ***
We still lack a good stack trace for this crash. Unfortunately, the attached stack traces are missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. If you are still able to reproduce this crash, can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 75788 [details] Stack trace of gedit crashing Hopefully this provides better information about the crash. Since the stack trace was more than 65k chars, I had to attach it as a text file. Cheers
Thank you very much Markus. Now I'm able to reproduce the crash using the file Markus attached in comment #5. It can be reproduced only if syntax highlighting is active, this is the reason why I failed to reproduce it before.
So I finally tracked this down: valgrind shows that memory corruption is involved. I am not sure why the crash gets triggered only under some conditions (some files and syntax highlighting), but the bug is in gtk. The problem was introduced with the patch of bug #317125. The following patch seems to fix the problem for me, though I am not sure it is the proper solution.
Created attachment 76040 [details] [review] proposed gtk patch
Looks good to me. Please commit to both branches.
done.
*** Bug 379654 has been marked as a duplicate of this bug. ***
*** Bug 384122 has been marked as a duplicate of this bug. ***
*** Bug 384713 has been marked as a duplicate of this bug. ***
*** Bug 396984 has been marked as a duplicate of this bug. ***
*** Bug 396990 has been marked as a duplicate of this bug. ***
*** Bug 401663 has been marked as a duplicate of this bug. ***
*** Bug 404524 has been marked as a duplicate of this bug. ***
*** Bug 404762 has been marked as a duplicate of this bug. ***
*** Bug 406393 has been marked as a duplicate of this bug. ***
*** Bug 412097 has been marked as a duplicate of this bug. ***
*** Bug 376146 has been marked as a duplicate of this bug. ***
*** Bug 412358 has been marked as a duplicate of this bug. ***
*** Bug 414284 has been marked as a duplicate of this bug. ***
*** Bug 415205 has been marked as a duplicate of this bug. ***
*** Bug 420229 has been marked as a duplicate of this bug. ***
*** Bug 427373 has been marked as a duplicate of this bug. ***
*** Bug 432896 has been marked as a duplicate of this bug. ***
*** Bug 439377 has been marked as a duplicate of this bug. ***
*** Bug 436629 has been marked as a duplicate of this bug. ***
*** Bug 363172 has been marked as a duplicate of this bug. ***
*** Bug 449390 has been marked as a duplicate of this bug. ***
*** Bug 451533 has been marked as a duplicate of this bug. ***
*** Bug 451534 has been marked as a duplicate of this bug. ***
*** Bug 460926 has been marked as a duplicate of this bug. ***
*** Bug 476105 has been marked as a duplicate of this bug. ***
*** Bug 482280 has been marked as a duplicate of this bug. ***
*** Bug 482663 has been marked as a duplicate of this bug. ***
*** Bug 483902 has been marked as a duplicate of this bug. ***