Segmentation Fault

[Thomas Werner]

I created a new event for Google but it crashed. Now on each start i get a segmentation fault on Ubuntu 14.04.

No idea howto debug:

Starting program: /usr/bin/maya-calendar
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe7178700 (LWP 28495)]
[New Thread 0x7fffe6977700 (LWP 28496)]
[New Thread 0x7fffdd668700 (LWP 28497)]
[_LOG_LEVEL_INFO 20:05:00.793842] Application.vala:153: Calendar version: 0.3
[_LOG_LEVEL_INFO 20:05:00.793903] Application.vala:155: Kernel version: 3.13.0-29-generic
[New Thread 0x7fffdcc2f700 (LWP 28499)]
[New Thread 0x7fffd3fff700 (LWP 28500)]
[New Thread 0x7fffd273b700 (LWP 28501)]
[Thread 0x7fffd3fff700 (LWP 28500) exited]
[New Thread 0x7fffd3fff700 (LWP 28502)]
[New Thread 0x7fffd1f3a700 (LWP 28503)]
[Thread 0x7fffd1f3a700 (LWP 28503) exited]
[New Thread 0x7fffd1f3a700 (LWP 28504)]
[New Thread 0x7fffbc68b700 (LWP 28505)]
[New Thread 0x7fffbbe8a700 (LWP 28506)]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff4ddce9d in maya_util_ecal_to_date_time () from /usr/lib/x86_64-linux-gnu/libmaya-calendar.so.0

[Steffen Schuhmann (sschuhmann)]

The bug is raised during the event creation from an ecal source. When the event times not changed maya only creates the start time for the event, the missing end time causing the crash.

Should we provide a default end time, e.g. a half hour, in the event creation?

[Raphael Isemann (teemperor)]

I think providing a default-duration for events with missing ending-time is a sane solution. Voting for 1 hour here as it would fit the Google calendar.

[Steffen Schuhmann (sschuhmann)]

In order to make the event creation "tolerant" i'll have to check if the end time is set. My first idea was to check if it's a null reference, which seems to be not possible in vala. I also couldn't catch any error in the process.

Is there any way to catch that sigsev only in this specific method or check if the object is accessible?