Your message dated Mon, 30 Dec 2013 15:58:38 +0000
with message-id <52c1982e.6040...@googlemail.com>
and subject line
has caused the Debian Bug report #733204,
regarding boinc-app-seti causes segfault in boinc-client on armel
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.)
--
733204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733204
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: boinc-app-seti
Version: 7.00~svn1933-1
Severity: grave
Usertags: unwarranted-self-importance-upstream
Control: found -1 boinc-client/7.2.33+dfsg-1
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu
Running the setiathome_advanced binary from boinc-app-seti (from
Unstable) on an armel chroot causes boinc-client to segfault immediately.
<core_client_version>7.2.33</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
boinc-app-seti is invoked with the following arguments:
--start
--end.
I: boinc_parse_init_data_file
I: boinc_get_init_data
I: boinc_init
I: worker
I: worker() - common_init
I: worker() - read_wu_state
SIGSEGV: segmentation violation
Stack trace (9 frames):
/usr/lib/libboinc.so.7(boinc_catch_signal+0xd8)[0x40078470]
/lib/arm-linux-gnueabi/libc.so.6(__default_sa_restorer_v2+0x0)[0x405b2bb0]
../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x658d0)[0x2a0658d0]
../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x24fbc)[0x2a024fbc]
../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x205d4)[0x2a0205d4]
../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x272d0)[0x2a0272d0]
../../projects/setiathome.berkeley.edu/setiathome_enhanced(+0x27660)[0x2a027660]
../../projects/setiathome.berkeley.edu/setiathome_enhanced(main+0x21c)[0x2a006de0]
/lib/arm-linux-gnueabi/libc.so.6(__libc_start_main+0x118)[0x4059c0cc]
Exiting...
</stderr_txt>
]]>
I have tried on multiple devices and even qemu-arm-static but the result
is always the same.
Upstream have a version which works natively with Android, so it should
be possible, although using the available binaries causes issues which I
have no yet looked into further.
The only other package to test is from Squeeze but that is too old
(version 5.x).
Originally reported at
http://setiathome.berkeley.edu/forum_thread.php?id=73619 which included
details of testing but removed by a childish moderator (reported).
--- End Message ---
--- Begin Message ---
Control: fixed -1 7.19~svn2050-2.is.7.00~svn1933-1
Never mind, it's finally shown up. I had no idea the queue on the build
machines were so long.
So far so good: no segfault and it is currently running.
--- End Message ---
