GNOME Bugzilla – Bug 746129
crash (SIGSEGV) while going to line 31948 in a large SQL dump
Last modified: 2015-03-22 11:08:24 UTC
Created attachment 299260 [details] gdb backtrace of the crash I'm using gedit 3.14.0-3 and GNOME 3.14 on Debian jessie. I got a crash while trying to go to line 31948 in a large SQL dump.
Thanks for the bug report. I copy/paste the backtrace in the comment so that bugzilla will display it nicely.
+ Trace 234837
Thread 1 (Thread 0x7f09d844d980 (LWP 24495))
> #3 ?? from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so Debug info is missing for gedit, it'd be useful to know the function there.
Unfortunately Debian doesn't distribute debug info for gedit, I'll file a bug in Debian asking for that. Please close the bug if the backtrace isn't useful enough.
Frame #3 is probably _gedit_cmd_search_goto_line(), but this function doesn't call directly gtk_text_iter_get_line() (at frame #2). gtk_text_iter_get_line() is most probably called in gedit-view-frame.c, more precisely in init_search_entry(). But I'm not 100% sure, and by reading the code I don't see what's wrong. And I cannot reproduce the crash when testing the goto line on a big file (e.g. just after loading it, when the view isn't fully rendered). So I'm closing the bug. If you have more information, like warning messages in the terminal, feel free to reopen.