evolution-calendar-factory crashed with SIGSEGV in icalarray_element_at()

[Chetan]

Appeared on startup doesn't come after that

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: evolution-data-server 3.10.1-2ubuntu2~saucy1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Thu Nov 28 23:56:37 2013
ExecutablePath: /usr/lib/evolution/evolution-calendar-factory
InstallationDate: Installed on 2013-04-26 (216 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/evolution/evolution-calendar-factory
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
SegvAnalysis:
 Segfault happened at: 0x7f5104854db3 <icalarray_element_at+19>: add (%rcx,%rsi,8),%rax
 PC (0x7f5104854db3) ok
 source "(%rcx,%rsi,8)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: evolution-data-server
StacktraceTop:
 icalarray_element_at () from /usr/lib/libical.so.1
 icaltimezone_get_utc_offset () from /usr/lib/libical.so.1
 icaltimezone_convert_time () from /usr/lib/libical.so.1
 icaltime_as_timet_with_zone () from /usr/lib/libical.so.1
 ?? () from /usr/lib/libecal-1.2.so.16
Title: evolution-calendar-factory crashed with SIGSEGV in icalarray_element_at()
UpgradeStatus: Upgraded to saucy on 2013-10-19 (40 days ago)
UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers

[Ubuntu GNOME (ug-bot)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1240938, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.