Bug 1239291
Summary: | [abrt] gnome-calendar: icaltimezone_compare_change_fn(): gnome-calendar killed by SIGSEGV | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | mariolinux | ||||||||||||||||||||||||
Component: | gnome-calendar | Assignee: | Igor Gnatenko <ignatenko> | ||||||||||||||||||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||||
Version: | 22 | CC: | fedora, gnome-sig, ignatenko, mariolinux, nicolas.laplante | ||||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/c597255ad66873fe3d85aa3cab30bce765cdd84b | ||||||||||||||||||||||||||
Whiteboard: | abrt_hash:f825e7b5476a8f01d2cae2359537aebd6dcd2099 | ||||||||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||||
Last Closed: | 2016-06-28 13:48:52 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
mariolinux
2015-07-05 12:08:02 UTC
Created attachment 1046206 [details]
File: backtrace
Created attachment 1046207 [details]
File: cgroup
Created attachment 1046208 [details]
File: core_backtrace
Created attachment 1046209 [details]
File: dso_list
Created attachment 1046210 [details]
File: environ
Created attachment 1046211 [details]
File: limits
Created attachment 1046212 [details]
File: maps
Created attachment 1046213 [details]
File: mountinfo
Created attachment 1046214 [details]
File: namespaces
Created attachment 1046215 [details]
File: open_fds
Created attachment 1046216 [details]
File: proc_pid_status
Looks like some memory corrupted in thred (not sure). stm = {tm_sec = 0, tm_min = 0, tm_hour = 0, tm_mday = 1, tm_mon = 0, tm_year = 0, tm_wday = 0, tm_yday = 0, tm_isdst = 36984752, tm_gmtoff = 139899971561937, tm_zone = 0xc000007b6 <error: Cannot access memory at address 0xc000007b6>} Are you able to reproduce this? (In reply to Igor Gnatenko from comment #12) > Looks like some memory corrupted in thred (not sure). > stm = {tm_sec = 0, tm_min = 0, tm_hour = 0, tm_mday = 1, tm_mon = 0, tm_year > = 0, tm_wday = 0, tm_yday = 0, tm_isdst = 36984752, tm_gmtoff = > 139899971561937, tm_zone = 0xc000007b6 <error: Cannot access memory at > address 0xc000007b6>} > > Are you able to reproduce this? I don't know how to reproduce this error. Old bug, if still reproducible - please reopen. Still reproducible. I can't reopen it, but I've reported a new one in bug #1409398. Is it possible that this bug is related to leap seconds? This bug happened after the leap second on 2015-06-31. My crasher (bug #1409398) happened on 2017-01-01, one day after the leap second introduced on 2016-12-31. See also: https://en.wikipedia.org/wiki/Leap_second |