Bug#721617: pyliblo: FTBFS on sparc: testSendOthers (unit.ServerTestCase) ... Bus error (core dumped)

[Felipe Sateler]

Hi liblo devs,

The python liblo wrapper has a test suite that has uncovered a bug in
liblo. More details below:

On Mon, Sep 2, 2013 at 1:56 PM, Sebastian Ramacher <sramacher at debian.org> wrote:
>
> On 2013-09-02 14:51:18, Sebastian Ramacher wrote:
>> Source: pyliblo
>> Version: 0.9.1-3
>> Severity: serious
>> Justification: FTBFS but built successfully in the past
>>
>> pyliblo FTBFS on sparc:
>> | PYTHONPATH=$(ls -d /home/sramacher/pyliblo-0.9.1/build/lib.*-2.7) \
>> |                 python2.7 -m unittest discover -s test/ -p '*.py' -v
>> | testHostPort (unit.AddressTestCase) ... ok
>> | testHostPortProto (unit.AddressTestCase) ... ok
>> | testPort (unit.AddressTestCase) ... ok
>> | testUrl (unit.AddressTestCase) ... ok
>> | testSendReceive (unit.DecoratorTestCase) ... ok
>> | testNoPermission (unit.ServerCreationTestCase) ... ok
>> | testPort (unit.ServerCreationTestCase) ... ok
>> | testPortProto (unit.ServerCreationTestCase) ... ok
>> | testRandomPort (unit.ServerCreationTestCase) ... ok
>> | testNotReachable (unit.ServerTCPTestCase) ... ok
>> | testSendReceive (unit.ServerTCPTestCase) ... ok
>> | testPort (unit.ServerTestCase) ... ok
>> | testRecvImmediate (unit.ServerTestCase) ... ok
>> | testRecvTimeout (unit.ServerTestCase) ... ok
>> | testSendBlob (unit.ServerTestCase) ... ok
>> | testSendBundle (unit.ServerTestCase) ... ok
>> | testSendInt (unit.ServerTestCase) ... ok
>> | testSendInvalid (unit.ServerTestCase) ... ok
>> | testSendMessage (unit.ServerTestCase) ... ok
>> | testSendOthers (unit.ServerTestCase) ... Bus error (core dumped)
>> | make[1]: *** [test-python2.7] Error 138
>>
>> I was able to reproduce this issue on smetana.d.o. liblo rebuilt with
>> debugging symbols gives me the following back trace:
>>
>> Core was generated by `python2.7 -m unittest discover -s test/ -p *.py -v'.
>> Program terminated with signal 10, Bus error.
>> #0  0x7056634c in lo_arg_network_endian (type=<error reading variable: Cannot access memory at address 0x47>,
>>     data=<error reading variable: Cannot access memory at address 0x4b>) at message.c:687
>> 687             *(int64_t *)data = lo_htoo64(*(int64_t *)data);
>> (gdb) bt
>> #0  0x7056634c in lo_arg_network_endian (type=<error reading variable: Cannot access memory at address 0x47>,
>>     data=<error reading variable: Cannot access memory at address 0x4b>) at message.c:687
>> #1  0x7036c008 in ?? () from /lib/sparc-linux-gnu/libc.so.6
>> #2  0x7036c008 in ?? () from /lib/sparc-linux-gnu/libc.so.6
>> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
>
> I've debugged this a bit further and it looks like liblo is broken on
> sparc. Using the two binaries shipped in liblo-tools, one can easily
> produce bus errors:
>
> In one shell run 'oscdump 54321', in the other 'oscsend localhost 54321
> /test hTfs 12345 3.14 hello' (this is the example from the oscsend with
> 64 bit instead of 32 bit integers) and oscdump immediately crashes with
> a bus error:
>
> Core was generated by `oscdump 54321'.
> Program terminated with signal 10, Bus error.
> #0  0xf7eed3ec in lo_arg_pp_internal () from /usr/lib/liblo.so.7
> (gdb) bt
> #0  0xf7eed3ec in lo_arg_pp_internal () from /usr/lib/liblo.so.7
> #1  0x0000000d in ?? ()
> #2  0x0000000d in ?? ()
>
> So this makes me believe that liblo is broken on sparc and hence I'm
> reassigning this bug to liblo.
>
> Regards
> --
> Sebastian Ramacher
>
> _______________________________________________
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers



-- 

Saludos,
Felipe Sateler