Bug 694118

Summary: Valgrind error messages from libical
Product: [Fedora] Fedora Reporter: Andris Pavenis <andris.pavenis>
Component: libicalAssignee: Robert Scheck <redhat-bugzilla>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mcrha, rdieter, redhat-bugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:14:31 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
Fix for valgrind error messages none

Description Andris Pavenis 2011-04-06 13:50:47 UTC 
Description of problem:

Valgrind outputs errors from libical about invalid read of size 8

Version-Release number of selected component (if applicable):

Fedora 14
libical-0.46-2.fc14.x86_64
valgrind-3.5.0-20.fc14.x86_64

How reproducible:

Always

Additional info:

Valgrind output:

==3203== Invalid read of size 8
==3203==    at 0x3A416386F9: icaltzutil_fetch_timezone (icaltz-util.c:441)
==3203==    by 0x3A41639758: icaltimezone_load_builtin_timezone (icaltimezone.c:1796)
==3203==    by 0x3A4163AEDF: icaltimezone_get_component (icaltimezone.c:1215)
==3203==    by 0x4C89522: sysync::finalizeSystemZoneDefinitions(sysync::GZones*) (platform_timezones.cpp:186)
==3203==    by 0x4D2CA34: sysync::GZones::loggingStarted() (timezones.cpp:114)
==3203==    by 0x4D06747: sysync::TSyncAppBase::finishConfig() (syncappbase.cpp:1445)
==3203==    by 0x4D06C4F: sysync::TSyncAppBase::readXMLConfigStream(int (*)(char*, unsigned long, unsigned long*, void*), void*) (syncappbase.cpp:1757)
==3203==    by 0x4D06DC1: sysync::TSyncAppBase::readXMLConfigFile(char const*) (syncappbase.cpp:1840)
==3203==    by 0x4CB0AC3: sysync::TEngineInterface::InitEngineFile(char const*) (engineinterface.cpp:1236)
==3203==    by 0x41E300: ipn::SyncServerEngine::init_engine_file(std::string const&) (SyncServerEngine.cpp:92)
==3203==    by 0x412083: start(unsigned int, std::string const&, std::string const&, std::string const&, std::string const&) (sync_server.cpp:50)
==3203==    by 0x41365E: main (sync_server.cpp:258)
==3203==  Address 0x5ece790 is 0 bytes after a block of size 0 alloc'd
==3203==    at 0x4A04896: calloc (vg_replace_malloc.c:418)
==3203==    by 0x3A41638124: icaltzutil_fetch_timezone (icaltz-util.c:339)
==3203==    by 0x3A41639758: icaltimezone_load_builtin_timezone (icaltimezone.c:1796)
==3203==    by 0x3A4163AEDF: icaltimezone_get_component (icaltimezone.c:1215)
==3203==    by 0x4C89522: sysync::finalizeSystemZoneDefinitions(sysync::GZones*) (platform_timezones.cpp:186)
==3203==    by 0x4D2CA34: sysync::GZones::loggingStarted() (timezones.cpp:114)
==3203==    by 0x4D06747: sysync::TSyncAppBase::finishConfig() (syncappbase.cpp:1445)
==3203==    by 0x4D06C4F: sysync::TSyncAppBase::readXMLConfigStream(int (*)(char*, unsigned long, unsigned long*, void*), void*) (syncappbase.cpp:1757)
==3203==    by 0x4D06DC1: sysync::TSyncAppBase::readXMLConfigFile(char const*) (syncappbase.cpp:1840)
==3203==    by 0x4CB0AC3: sysync::TEngineInterface::InitEngineFile(char const*) (engineinterface.cpp:1236)
==3203==    by 0x41E300: ipn::SyncServerEngine::init_engine_file(std::string const&) (SyncServerEngine.cpp:92)
==3203==    by 0x412083: start(unsigned int, std::string const&, std::string const&, std::string const&, std::string const&) (sync_server.cpp:50)
==3203==

Also I see the same problem in CentOS 5.5 which is RHEL 5.5 clone.
Comment 1 Andris Pavenis 2011-04-06 14:02:46 UTC 
Created attachment 490291 [details]
Fix for valgrind error messages

I rebuilt libical including the attached patch to workaround the problem.
Comment 2 Fedora End Of Life 2012-08-16 15:14:34 UTC 
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping