Bug 435155 – crash in Text Editor: Editing some C code

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 435155 - crash in Text Editor: Editing some C code


Summary:	crash in Text Editor: Editing some C code


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-05-02 11:59 UTC by trashotron
Modified:	2007-05-03 12:44 UTC

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

Description trashotron 2007-05-02 11:59:13 UTC

Version: 2.16.1

What were you doing when the application crashed?
Editing some C++ code


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

Memory status: size: 105267200 vsize: 0 resident: 105267200 share: 0 rss: 28102656 rss_rlim: 0
CPU usage: start_time: 1178105050 rtime: 0 utime: 1247 stime: 0 cutime:1201 cstime: 0 timeout: 46 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 -1226836304 (LWP 4961)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 131868

Thread 1 (Thread -1226836304 (LWP 4961))

#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
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_text_buffer_cut_clipboard
from /usr/lib/libgtk-x11-2.0.so.0
#12 _gtk_marshal_VOID__OBJECT_BOXED_BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#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_notify_will_remove_tag
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
from /usr/lib/libgtksourceview-1.0.so.0
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-05-03 12:44:55 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

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