Opened 7 years ago

Closed 6 years ago

#1549 closed defect (fixed in core)

ffalarms segfaults: libical segfaults in icaltimezone_get_builtin_timezone

Reported by: lukpank Owned by: mrmoku
Priority: major Milestone:
Component: SHR Image Version: SHR-core
Keywords: Cc:


ffalarms in the image 20111121 segfaults. This comes from libical segfaulting in function icaltimezone_get_builtin_timezone. The simple call reveals the segfault

#include <libical/ical.h>

int main()
	icaltimezone_get_builtin_timezone ("Europe/Warsaw");

compile this with (in some devshell):

$CC -lical icaltest.c -o icaltest

Change History (7)

comment:1 Changed 7 years ago by lukpank

The problem is that package tzdata (version 2011g-r10.0) should ship the file /usr/share/zoneinfo/ But the file is not shipped and so libical cannot find it and segfaults in the call to function icaltimezone_get_builtin_timezone. ships the file only if LIBC is equal to "eglibc". I suppose the variable LIBC is not set at all.
I have a problem to fetch tzdata-2011g-r10.0 so I cannot check it.

comment:2 Changed 6 years ago by GNUtoo

I'll try to look at it very soon,
I want alarms to work so badly....


comment:3 Changed 6 years ago by GNUtoo

there was a patch for removing the tzdata from meta-openembedded and use the more recent one from openembedded-core(that also lacks the LIBC thing).

let me look....

comment:4 Changed 6 years ago by GNUtoo

the patch required extra work to be done on the tzdata that is in openembedded core, which have been made and submitted.

So it should be fixed soon.


comment:5 Changed 6 years ago by jama

I've added patch to meta-oe/shr to drop tzdata/tzinfo from there, so in 026 we should be able to test those changes from oe-core.

comment:6 Changed 6 years ago by jama

Tested on target with

SHR root@gjama / $ opkg install libical-dev
Installing libical-dev (0.48-r0) to root...
Configuring libical-dev.
SHR root@gjama / $ gcc -lical icaltest.c -o icaltest
SHR root@gjama / $ ./icaltest

comment:7 Changed 6 years ago by GNUtoo

  • Resolution set to fixed in core
  • Status changed from new to closed

it's fixed now(by JaMa?).


Note: See TracTickets for help on using tickets.