valgrind error on ARM system

Bug #1251104 reported by João M. S. Silva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pixman (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is on an ARM system. The error I get is:

==1032== Invalid read of size 1
==1032== at 0x4830D4C: strncmp (mc_replace_strmem.c:547)
==1032== by 0x6A048B3: have_feature (pixman-arm.c:167)
==1032== by 0x6A0494D: _pixman_arm_get_implementations (pixman-arm.c:210)
==1032== by 0x6A0FC9F: _pixman_choose_implementation (pixman-implementation.c:367)
==1032== by 0x69DED55: pixman_constructor (pixman.c:39)
==1032== by 0x400B02B: call_init (dl-init.c:84)
==1032== by 0x400B0AB: _dl_init (dl-init.c:133)
==1032== by 0x4000C61: ??? (in /lib/arm-linux-gnueabihf/ld-2.17.so)
==1032== Address 0xbee26640 is not stack'd, malloc'd or (recently) free'd

I'm not sure whether this bug is from libpixman or valgrind. Please advise.

On Intel-based systems there is no valgrind error.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.