Your message dated Fri, 31 Jan 2014 13:46:48 -0300 with message-id <caafdzj8cox2yg2pk7+hfemgxdgopavjwc7ddg-he7e7xy_z...@mail.gmail.com> and subject line Liblo is no longer in sparc has caused the Debian Bug report #721617, regarding liblo7: broken on sparc: bus error while sending 64 bit integers to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 721617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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?) Regards -- Sebastian Ramacher
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---Version: 0.26~repack-8 Closing because liblo is no longer in sparc, and will not be built again there. -- Saludos, Felipe Sateler
--- End Message ---
