GNOME Bugzilla – Bug 699826
Anjuta 3.8.1 segfaults when trying to build any project.
Last modified: 2020-11-06 20:22:17 UTC
Created attachment 243477 [details] Backtrace of report. It's my first time using Anjuta and learning Vala. I have valac 0.20.1 installed along with Anjuta 3.8.1 on a fresh Arch Linux install. Projects compile successfully using valac but when attempting to build or check with Anjuta, it segfaults with the following terminal output: (anjuta:1595): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_subpixbuf: assertion `src_x >= 0 && src_x + width <= src_pixbuf->width' failed (anjuta:1595): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (anjuta:1595): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `GDK_IS_PIXBUF (pixbuf)' failed (anjuta:1595): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `GDK_IS_PIXBUF (pixbuf)' failed (anjuta:1595): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_pixels: assertion `GDK_IS_PIXBUF (pixbuf)' failed (anjuta:1595): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `GDK_IS_PIXBUF (pixbuf)' failed (anjuta:1595): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `GDK_IS_PIXBUF (pixbuf)' failed [1] 1595 segmentation fault (core dumped) anjuta Attached is a backtrace. (I hope I did it right)
Created attachment 243480 [details] ldd of anjuta Don't know if this helps.
Thanks for your report. I have tried to build a project in Vala using valac 0.20.1 and I haven't seen this issue. I have created the project using the project wizard, keeping all settings to their default value. I have clicked on Build->Build Project, the project is built without error, just two warnings. Finally, I click on Run->Run and I get an empty window which is the expected result. Could you do exactly the same on your system? Could you describe more in details how you get the issue? I'm not sure it's related to Vala and there is nothing specific to Anjuta in the backtrace. It could be a memory corrupted by Anjuta but it will be difficult to track.
Hi Sébastien, thanks for the response. This happens when building a default, empty project with all settings default. I also tried a few Hello World examples from Vala documentation on live.gnome.org. I reformatted my computer and reinstalled Arch Linux and Ubuntu Gnome 13.04, each time same effect. I can use Anjuta for editing but I have resorted to using valac in terminal for compiling.
(In reply to comment #3) > I reformatted my computer and reinstalled Arch Linux and Ubuntu Gnome 13.04, > each time same effect. I think reinstalling the system for such issue is overkill. > I can use Anjuta for editing but I have resorted to using valac in terminal for > compiling. By example when you click on Build->Build Project, Anjuta is running make in the project directory. So if you do the same in a terminal (go inside the project directory and run 'make'), is it working fine?
(In reply to comment #3) > I reformatted my computer and reinstalled Arch Linux and Ubuntu Gnome 13.04, > each time same effect. I'm using Gnome Shell in Ubuntu 13.04 about a month ago and I don't have this issue.
(In reply to comment #4) > I think reinstalling the system for such issue is overkill. I wasn't sure if the issue was distro specific, just wanted to be sure. > By example when you click on Build->Build Project, Anjuta is running make in > the project directory. So if you do the same in a terminal (go inside the > project directory and run 'make'), is it working fine? In terminal, I can successfully run autogen.sh and make and execute the application(after moving it up from the src directory). Are there any suggested methods to identify what's going on? If this bug seems isolated, I'll gladly wait to see what happends in future releases. I hope I'm the only one experiencing this, Anjuta looks really promising, and so does vala.
Oh, I should also add, I tried the same install procedures, identical packages, on another machine and everything works smoothly. I don't know enought yet to claim that it might be a low-level issue, is it possible?
(In reply to comment #7) > Oh, I should also add, I tried the same install procedures, identical packages, > on another machine and everything works smoothly. I don't know enought yet to > claim that it might be a low-level issue, is it possible? I don't know neither. > Are there any suggested methods to identify what's going on? Perhaps you can try to compile glib, gdk and gtk with debugging information and without optimization (add 'CFLAGS=-g -O0' to configure or autogen arguments). There is a good chance that the bug disappears but if not (which is the best case), you can run anjuta with gdb and get more details about what is wrong: which variable and then try to find why looking at the source code. But the backtrace should already be more detailed. > I hope I'm the only one experiencing this Me too. We will keep this bug open and see if there are additional reports.
I had the same problem. Maybe this can help a little bit. I fixed it but cannot reconstruct it. Everytime I opened anjuta it also opens a file from another Projekt I worked on earlier (GDLSample.vala). When I tried building anjuta crashed. I tried to close this file before building, but it doesn't help. So I close the project "File->CloseProject" and then close this file(GDLSample.vala). After restarting anjuta I opened my project. Now this file doesnt open I can build my project. Hope this helps ...
(In reply to comment #9) > Hope this helps ... Thank you for these additional informations but I don't see how this would cause a bug when building the project. Could you reopen this file GDLSample.vala with your project to see if it crashes again. You should be able to do the following 1. Open anjuta which should load your project. 2. Close the project 3. Open GDLSample.vala 4. Open again your project > The file GDLSample.vala should be still here 5. Close Anjuta 6. Now we your re open Anjuta, you should get your project files and this additional GDLSample.vala file. > Does it still crash?
Thanks, Tschux, but that didn't solve my problem. The crash still happens whenever I click on the "Execute" button in the dialog for Build (src); Build Project; Check Module; Check Project; Configure Project; Install Project etc. I edited the title as this is apparent for any project for any language.
(In reply to comment #11) > The crash still happens whenever I click on the "Execute" button in the dialog > for Build (src); Build Project; Check Module; Check Project; Configure Project; > Install Project etc. Do you get a crash if you configure your project outside Anjuta? Run autogen.sh in your source directory then open Anjuta and select the default configuration which is using the source directory as the build directory. If you select Build, you shouldn't get a dialog and the project should build without a crash. Is it happening a simple C project, by example the C Gtk simple one? Then, If it crashes, could you build Anjuta from sources by example the master version that you can take directly from git? If it still crashes, I can try to add debugging message to understand what's happen. It could be long but we should be able to fix this.
I just upgraded to 3.12 and still... Anjuta crashes when attempting to build/execute a project. Even the simple C Gtk example. I will build Anjuta master now to test. I am unfamiliar with which debug flags I should set, if any.
Created attachment 274641 [details] Terminal output of Anjuta 3.12
Created attachment 274662 [details] Trace of Anjuta 3.12
Okay... this is going to sound strange but please bear with me... Anjuta does not segfault when I use the Numix-Square icon theme. It segfaults with the default GNOME icon set as well as all the other icon sets I have used the last year. I discovered this by mistake and I have been running it over and over again to make sure but this is really the only variable. To me this makes no sense to me. Maybe it does to a developer. Anyway, I am stoked that I can finally use Anjuta outside of a virtual machine.
Hmm, the crash is pretty deep inside gdk/gtk. As it works in the virtual machine I suspect it it related to some library problem in your system that is triggered by anjuta.
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/anjuta/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.