Bug 400767 – crash in Text Editor: Editing mxml-file and pr...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 400767 - crash in Text Editor: Editing mxml-file and pr...


Summary:	crash in Text Editor: Editing mxml-file and pr...


Status:	RESOLVED DUPLICATE of bug 363172

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-25 20:45 UTC by Katja Viljakainen
Modified:	2007-03-24 11:09 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Attachments
stack trace with debugging symbols (8.02 KB, text/plain) 2007-01-25 23:35 UTC, Katja Viljakainen	Details
screenshot of freezed gedit (2.54 KB, image/png) 2007-01-25 23:43 UTC, Katja Viljakainen	Details

Description Katja Viljakainen 2007-01-25 20:45:10 UTC

Version: 2.16.1

What were you doing when the application crashed?
Editing mxml-file and pressing ctrl + z to undo typo.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 115879936 vsize: 0 resident: 115879936 share: 0 rss: 28524544 rss_rlim: 0
CPU usage: start_time: 1169753049 rtime: 0 utime: 6017 stime: 0 cutime:5687 cstime: 0 timeout: 330 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 -1227094352 (LWP 25406)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 105246

Thread 1 (Thread -1227094352 (LWP 25406))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 _gtk_text_btree_tag
at gtktextbtree.c line 1872
#11 gtk_text_buffer_real_remove_tag
at gtktextbuffer.c line 2289
#12 _gtk_marshal_VOID__OBJECT_BOXED_BOXED
at gtkmarshalers.c line 1922
#13 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 gtk_text_buffer_emit_tag
at gtktextbuffer.c line 2347
#19 ??
from /usr/lib/libgtksourceview-1.0.so.0
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
#48 ??
#49 ??
#50 ??
#51 ??
#0 __kernel_vsyscall

Comment 1 Bruno Boaventura 2007-01-25 22:26:25 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that 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!

Comment 2 Katja Viljakainen 2007-01-25 23:35:16 UTC

Created attachment 81235 [details]
stack trace with debugging symbols

Comment 3 Katja Viljakainen 2007-01-25 23:41:10 UTC

I hope I did it right. First time :) If need something more just tell me. Now it went different when tried to repeat that bug, it didn't shutdown and give bug buddy like before, now it freezed after I did copypaste (not even big file I edited, I can send it to you if it helps) and then undo using shortcuts.

I put screenshot as attachment also so you can see what I mean freezing.

Comment 4 Katja Viljakainen 2007-01-25 23:43:00 UTC

Created attachment 81236 [details]
screenshot of freezed gedit

Comment 5 Bruno Boaventura 2007-01-25 23:57:48 UTC

Very good trace! Thanks.

Comment 6 Paolo Maggi 2007-03-24 11:09:18 UTC


*** This bug has been marked as a duplicate of 363172 ***