Uff, ok t here is a bunch of documentation left to read.
However, here is the line:
g_object_set_data(G_OBJECT(args.detect.selection[0]), "vector-layer",
vector_layer[0]);
where:
args.detect.selection is : GwySelection *selection[2];
vector_layer[0] is : GwyVectorLayer *vector_layer[3];
This line works fine in gwyddion-stable.
I let the plugin run with G_DEBUG=fatal-criticals environment, but the core
dump doesn't get more information.
On 0, "David Nečas (Yeti)" <[email protected]> wrote:
> On Mon, Sep 15, 2014 at 11:06:44AM +0200, Mathias Müller wrote:
> > ok, here we go: I recompiled the snapshot with
> > G_DEBUG=fatal-criticals....but still the symbols are missing somehow.
>
> This is a run-time environment variable to make it dump core on critical
> errors. It makes no difference on compilation.
>
> https://developer.gnome.org/glib/stable/glib-running.html#G-DEBUG:CAPS
>
> > #2 0x00007f247e22e186 in test_plugin (current_data=0x0, run=GWY_RUN_NONE)
> > at fft_plugin.c:222
>
> Well, here's where it fails. So look at line 222 in your module.
>
> Compiling Gwyddion or the module with -Og -ggdb can help to make sense
> of the backtrace but does not seem necessary right now.
>
> Regards,
>
> Yeti
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Gwyddion-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gwyddion-users
