Bug 650210

Summary: [abrt] evolution-2.32.0-2.fc14: __strlen_sse2: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Farid <djfarid>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: lucilanga, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d136457e6cc9c8f58f8b0b1206d2bbd71334b941
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-05 15:05:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Farid 2010-11-05 14:20:37 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/evolution/2.32/evolution-alarm-notify
component: evolution
crash_function: __strlen_sse2
executable: /usr/libexec/evolution/2.32/evolution-alarm-notify
kernel: 2.6.35.6-48.fc14.x86_64
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/libexec/evolution/2.32/evolution-alarm-notify was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288966741
uid: 500

How to reproduce
-----
1.
2.
3.
This happens every time I log in.
Comment 1 Farid 2010-11-05 14:20:40 UTC 
Created attachment 458100 [details]
File: backtrace
Comment 2 Milan Crha 2010-11-05 15:05:23 UTC 
#2  0x0000003f680394cd in icaltimezone_get_builtin_timezone (location=0x0) at icaltimezone.c:1372
        zone = <value optimized out>
        lower = <value optimized out>
        zone_location = <value optimized out>
#3  0x000000000040bbc8 in config_data_get_timezone () at config-data.c:219
        location = 0x1c1ab80 "Europe/Stockholm"
        key = <value optimized out>

Thanks for a bug report. I do not understand this, the #3 has 'location' "Europe/Stockholm", but the backtrace shows it is passing location=0x0 to #2, but the code _is_ using the same 'location'. Maybe related to bug #649585.

I'm marking this as a duplicate of it, as another way how to reproduce it.

*** This bug has been marked as a duplicate of bug 649585 ***