Bug 569999 – Crash in anjuta at startup

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 569999 - Crash in anjuta at startup


Summary:	Crash in anjuta at startup


Status:	RESOLVED NOTABUG

Product:	anjuta
Classification:	Applications
Component:	core application
Version:	SVN TRUNK
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Naba Kumar
QA Contact:	Anjuta maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-01-31 17:43 UTC by Ignacio Casal Quinteiro (nacho)
Modified:	2009-02-05 12:46 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Ignacio Casal Quinteiro (nacho) 2009-01-31 17:43:06 UTC

When I start anjuta from a terminal I get:
nacho@ansalon:~/Projects/anjuta$ anjuta

(anjuta:7321): Gtk-WARNING **: SendSignal: missing action ActionDmaSignalSend

(anjuta:7321): Gtk-WARNING **: UpdateSignalList: missing action ActionDmaSignalUpdate

(anjuta:7321): Gtk-WARNING **: UpdateShlList: missing action ActionDmaSharedlibsUpdate
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f997741ba33, pid=7321, tid=140297200531408
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.0-b16 interpreted mode linux-amd64)
# Problematic frame:
# C  [libgio-2.0.so.0+0x1fa33]
#
# An error report file with more information is saved as:
# /home/nacho/Projects/anjuta/hs_err_pid7321.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted (core dumped)


And the backtrace:

Program received signal SIGSEGV, Segmentation fault.

+ Trace 212067

Thread 140568332212176 (LWP 8243)

#0 g_dummy_file_get_path
at /build/buildd/glib2.0-2.19.5/gio/gdummyfile.c line 151
#1 on_project_root_added
at plugin.c line 1603
#2 value_added_cb
at anjuta-plugin.c line 371
#3 IA__g_closure_invoke
at /build/buildd/glib2.0-2.19.5/gobject/gclosure.c line 767
#4 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.19.5/gobject/gsignal.c line 3244
#5 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.19.5/gobject/gsignal.c line 2977
#6 IA__g_signal_emit_by_name
at /build/buildd/glib2.0-2.19.5/gobject/gsignal.c line 3071
#7 on_profile_scoped
at plugin.c line 1409
#8 IA__g_closure_invoke
at /build/buildd/glib2.0-2.19.5/gobject/gclosure.c line 767
#9 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.19.5/gobject/gsignal.c line 3244
#10 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.19.5/gobject/gsignal.c line 2977
#11 IA__g_signal_emit_by_name
at /build/buildd/glib2.0-2.19.5/gobject/gsignal.c line 3071
#12 anjuta_profile_manager_load_profile
at anjuta-profile-manager.c line 463
#13 anjuta_new
at anjuta.c line 470
#14 main
at main.c line 392

Comment 1 Ignacio Casal Quinteiro (nacho) 2009-01-31 17:46:32 UTC

Removing the .cache/anjuta dir fixes the problem, so I can imagin this problem is because it cannot load the project. I removed the project that it was trying to load. So you should have a look at that.

Comment 2 Ignacio Casal Quinteiro (nacho) 2009-01-31 18:01:17 UTC

Loading a project I get the crash again.

Comment 3 Sébastien Granjoux 2009-02-01 09:59:18 UTC

I don't get these bugs. I fixed the first 3 warnings yesterday but I don't think it explains the crash anyway.

I don't know why Java VM comes here.

Comment 4 Johannes Schmid 2009-02-01 14:41:53 UTC

Well, the JavaVM most likely comes from libgda (you can build it without java), but it's just the sigsegv-handler of Java, nothing related to this bug.

Maybe a bug in unstable glib or something like that. I don't get it.

Comment 5 Johannes Schmid 2009-02-05 08:50:39 UTC

Do you still get his? Could be unstable glib or something like that.

Comment 6 Ignacio Casal Quinteiro (nacho) 2009-02-05 09:31:41 UTC

With latest revision is already crashing, anyway this looks more a problem with my unstable libraries than a programming problem. I tried several things to fix it but I couldn't find the problem, maybe something in gbf that is messing uris, but I don't know. I would close this as not a bug, at least not a bug of anjuta.