Re: [anjuta-devel] Help with fixing Anjuta crash

[Harish U <harishspqr gmail com>]

Hi Sebastien,

Adding dconf fixed the issue with preferences not getting saved. 

It appears like I am facing the same issue as the bug 740497. Was this bug fixed ? I am wondering if I am missing any dependency like I did (with dconf). Do you have any idea from the below stack trace and attached warnings file ? 

I have attached the stack trace below(top 7 frames):

#0  build_configuration_get_name (cfg=0x0) at configuration-list.c:394

#1  0x00007fffdfdf78a1 in build_configure_dialog (plugin=0x55555577fab0, func=0x0, file=0x0, 

    callback=0x0, user_data=0x0, error=0x0) at build.c:1195

#2  0x00007ffff26721a8 in g_closure_invoke (closure=0x555556a25b80, return_value=0x0, 

    n_param_values=1, param_values=0x7fffffffdad0, invocation_hint=0x7fffffffda70) at gclosure.c:768

#3  0x00007ffff26833cd in signal_emit_unlocked_R (node=node entry=0x555555a26440, 

    detail=detail entry=0, instance=instance entry=0x5555567d3270, 

    emission_return=emission_return entry=0x0, 

    instance_and_params=instance_and_params entry=0x7fffffffdad0) at gsignal.c:3553

#4  0x00007ffff268b0b8 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, 

    detail=<optimized out>, var_args=var_args entry=0x7fffffffdc58) at gsignal.c:3309

#5  0x00007ffff268b372 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, 

    detail=<optimized out>) at gsignal.c:3365

#6  0x00007ffff6e59470 in ?? () from /lib/libgtk-3.so.0

#7  0x00007ffff26723d7 in _g_closure_invoke_va (closure=0x5555557905a0, return_value=0x0, 

    instance=0x555556a42710, args=0x7fffffffdf28, n_params=0, param_types=0x0) at gclosure.c:831

#0  build_configuration_get_name (cfg=0x0) at configuration-list.c:394

394 return cfg->name;

#1  0x00007fffdfdf78a1 in build_configure_dialog (plugin=0x55555577fab0, func=0x0, file=0x0, 

    callback=0x0, user_data=0x0, error=0x0) at build.c:1195

1195 old_config_name = build_configuration_get_name (build_configuration_list_get_selected (plugin->configurations));

(gdb) print plugin

$1 = (BasicAutotoolsPlugin *) 0x55555577fab0

(gdb) print plugin->configurations

$2 = (BuildConfigurationList *) 0x5555560ba4a0

(gdb) print plugin->configurations->cfg

$3 = (BuildConfiguration *) 0x0

(gdb) print plugin->configurations->selected

$4 = (BuildConfiguration *) 0x0

(gdb) print plugin->configurations->project_root_uri

$5 = (gchar *) 0x555556a76b20 "file:///root/scratch/simpleC3”

#2  0x00007ffff26721a8 in g_closure_invoke (closure=0x555556a25b80, return_value=0x0, 

    n_param_values=1, param_values=0x7fffffffdad0, invocation_hint=0x7fffffffda70) at gclosure.c:768

768      marshal (closure,

I could see couple of directories 

Attachment: AnjutaWarnings.txt
Description: Text document

This is what happens when I try to build a project as soon as I launch Anjuta. If I close the project and re-open the same project, the build configurations are loaded correctly when I debug it. 

Thanks,

Harish

On Jul 29, 2015, at 10:34 AM, Sébastien Granjoux <seb sfo free fr> wrote:

Hi,

Le 29/07/2015 00:36, Harish U a écrit :

The issues noticed:
1. Anjuta does not seem to save preferences when I quit. It asks which
editor to use every time it launches.
2. Anjuta crashes when I try to build a project that was already open by
default when anjuta launches. It does not crash if I open a
project/create new project after launching Anjuta.
The reason for the crash appears to do with the failure to load the
build configurations when Anjuta starts. (Any thread sync issue ?)
3. Also autotools plugin is not enabled by default when Anjuta launches
even if I enable it in the preferences.
4. Strangely everything works fine as expected if I start Anjuta ->
close the project loaded by default -> then re-open the same project
from recent projects menu. If I do this, the build configurations are
loaded as expected(so this workaround fixes the crash issue)

I suspect that while exiting Anjuta settings are not correctly
persisted/saved.

Please let me know if you can think of any reasons as to why I see this
behaviour and how I could fix this.

Is it something similar to this bug:
https://bugzilla.gnome.org/show_bug.cgi?id=740497 ?

I don't get those issues here. If you can, it would be useful to check exactly what's happen with a debugger.

Let's start with the first issue.

1. Create a file foo.txt
2. Open it with Anjuta running 'anjuta -c -n -f foo.txt'
3. Select Edit->Preferences->Preferred plugin, click Forget selected plugin
4. Close Anjuta window

5. Open it with Anjuta running 'anjuta -c -n -f foo.txt'
6. You should have a dialog asking you which editor to use, choose one and check Remember this selection.
7. You should see your file opened
8. Close Anjuta window

9. Open it with Anjuta running 'anjuta -c -n -f foo.txt'
10. You should directory see your file opened with the selected editor
11. In Edit->Preferences->Preferred plugin, you should see it
12. Open dconf-editor
13. The key org.gnome.anjuta.remembered-plugins should be anjuta-editor:EditorPlugin,anjuta-sourceview:SourceviewPlugin,=anjuta-editor:EditorPlugin; if you use Scintilla as default.

Could you do all these steps and check where it fails, I suppose at step 10.


Regards,

Sébastien