mysql-query-browser crashed with SIGSEGV in gtk_text_iter_forward_line()

[Yura Tolstik]

mysql query browser crashed on lucid

ProblemType: Crash
Architecture: i386
Date: Sat Feb 27 11:44:06 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/mysql-query-browser
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: mysql-query-browser 5.0r14+openSUSE-2build1
ProcCmdline: /usr/bin/mysql-query-browser
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x52c5db7: mov 0x28(%eax),%eax
 PC (0x052c5db7) ok
 source "0x28(%eax)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mysql-gui-tools
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_text_iter_forward_line ()
 Gtk::TextIter::forward_line() ()
 MGSQLTextBuffer::do_hiliting() ()
Title: mysql-query-browser crashed with SIGSEGV in gtk_text_iter_forward_line()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #521458, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.