On Fr, 2012-09-07 at 09:11 +0300, Alberto Mardegan wrote:
> Hi all,
> when running my application under gdb I get the following:
>
> =============
> > Program received signal SIGSEGV, Segmentation fault.
> > publishing_ui_publishing_dialog_account_service_copy (self=self@entry=0x0,
> > dest=dest@entry=0x7fffffffcae0)
> > at
> > /media/mardy/Data/src/bzr/shotwell/build-area/shotwell-0.12.90/src/publishing/PublishingUI.vala:133
> > 133 private struct AccountService {
> > (gdb) bt
> > #0 publishing_ui_publishing_dialog_account_service_copy
> > (self=self@entry=0x0, dest=dest@entry=0x7fffffffcae0)
> > at
> > /media/mardy/Data/src/bzr/shotwell/build-area/shotwell-0.12.90/src/publishing/PublishingUI.vala:133
> > #1 0x00000000004e1f25 in
> > publishing_ui_publishing_dialog_on_service_changed
> > (self=self@entry=0xa5e2a0)
> > at
> > /media/mardy/Data/src/bzr/shotwell/build-area/shotwell-0.12.90/src/publishing/PublishingUI.vala:415
> [...]
> =============
>
> "publishing_ui_publishing_dialog_account_service_copy" is a C function
> generated by Vala. However, if I type "list" in gdb all I see is the
> definition of my "struct AccountService".
> I would like to be able to see a backtrace with the C functions, and be
> able to navigate through them.
> Any hints?
Don't pass -g to valac. The yorba guys might know how to do that nicely
in shotwell without disabling C debug.
_______________________________________________
vala-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/vala-list
