Bug 687646 – Auto-completion causes a segfault in Anjuta 3.6.1

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 687646 - Auto-completion causes a segfault in Anjuta 3.6.1


Summary:	Auto-completion causes a segfault in Anjuta 3.6.1


Status:	RESOLVED FIXED

Product:	anjuta
Classification:	Applications
Component:	plugins: language-support-python
Version:	3.6.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Anjuta maintainers
QA Contact:	Anjuta maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-11-05 14:10 UTC by Peteris Krisjanis
Modified:	2012-11-18 14:16 UTC

See Also:	https://bugzilla.redhat.com/show_bug.cgi?id=872745
GNOME target:	---
GNOME version:	---

Description Peteris Krisjanis 2012-11-05 14:10:27 UTC

This is reproducable on Fedora 18 beta with 05.11.2012 updates

1. Install python-rope as 'yum install python-rope'
2. Open Anjuta
3. Try to write fast something what could use auto-completion. I created Gtk+ element, and just tried to add .show() function (like window.show()).
4. Anjuta crashes on segfault

Program received signal SIGSEGV, Segmentation fault.
0x41f3820b in g_type_check_instance_cast (type_instance=0x8da84e8, iface_type=148541640) at gtype.c:3998
3998		  is_instantiatable = node && node->is_instantiatable;
(gdb) bt

+ Trace 231135

#0 g_type_check_instance_cast
at gtype.c line 3998
#1 completion_function
from /usr/lib/anjuta/libanjuta-language-support-python.so
#2 g_completion_complete
at deprecated/gcompletion.c line 390
#3 python_assist_update_autocomplete
from /usr/lib/anjuta/libanjuta-language-support-python.so
#4 on_autocomplete_finished
from /usr/lib/anjuta/libanjuta-language-support-python.so
#5 anjuta_cclosure_marshal_VOID__INT_INT_ULONG
from /lib/libanjuta-3.so.0
#6 g_closure_invoke
at gclosure.c line 777
#7 signal_emit_unlocked_R
at gsignal.c line 3551
#8 g_signal_emit_valist
at gsignal.c line 3300
#9 g_signal_emit_by_name
at gsignal.c line 3393
#10 anjuta_launcher_execution_done_cleanup
from /lib/libanjuta-3.so.0
#11 anjuta_launcher_check_for_execution_done
from /lib/libanjuta-3.so.0
#12 g_timeout_dispatch
at gmain.c line 4026
#13 g_main_dispatch
at gmain.c line 2715
#14 g_main_context_dispatch
at gmain.c line 3219
#15 g_main_context_iterate
at gmain.c line 3290
#16 g_main_context_iteration
at gmain.c line 3351
#17 g_application_run
at gapplication.c line 1624

Comment 1 Johannes Schmid 2012-11-05 21:14:49 UTC

Thanks for your report - looks completely reproducible to me - I am looking into it.

Comment 2 Johannes Schmid 2012-11-18 14:16:22 UTC

Thanks for your report, I fixed this in master and gnome-3-6 branch!

http://git.gnome.org/browse/anjuta/commit/?id=00521151148ca494107fe7ea12e64576476887de