Re: Bug#851412: FTBFS on mips*, tests fail with SIGSEGV
On Sun, Jan 15, 2017 at 1:15 AM, Michael Biebl <biebl@debian.org> wrote:
> Am 14.01.2017 um 18:02 schrieb Michael Biebl:
>
>> binutils_2.27.90.20170114-1. Building in stretch chroot though was
>> successful. So my observation is:
>>
>> binutils_2.27.90.20170114-1: fails
>> binutils_2.27.90.20170113-1: fails
>> binutils_2.27.51.20161220-1: ok
>>
>> So it looks like a mips related regression in binutils at a first
>> glance. In the past, systemd built reasonably reliably on mips* [3].
>
> A notable difference (aside from binutils) between the sid and stretch
> chroot is gcc-6, which is at version 6.2.1-5 in stretch and 6.3.0-2 in
> unstable.
> I couldn't test this combination (old binutils + new gcc) on the porter
> boxes though.
>
I tried to build a package libsystemd0-dbgsym, and test it with gdb,
it seems all binary linked with libsystemd will fail.
root@thor:/tmp# gdb /usr/bin/top
GNU gdb (Debian 7.12-4) 7.12
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips64el-linux-gnuabi64".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/top...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/top
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/mips64el-linux-gnuabi64/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
_IO_new_fclose (fp=0x1) at iofclose.c:48
48 iofclose.c: No such file or directory.
(gdb) bt
#0 _IO_new_fclose (fp=0x1) at iofclose.c:48
#1 0x000000fff7c96d28 in _init () from
/lib/mips64el-linux-gnuabi64/libsystemd.so.0
#2 0x000000fff7fdb9d0 in call_init (l=0xfff7fc4120,
argc=argc@entry=1, argv=argv@entry=0xfffffff5c8,
env=env@entry=0xfffffff5d8) at dl-init.c:58
#3 0x000000fff7fdbba8 in call_init (env=0xfffffff5d8,
argv=0xfffffff5c8, argc=1, l=<optimized out>) at dl-init.c:30
#4 _dl_init (main_map=0xfff7fff848, argc=<optimized out>,
argv=0xfffffff5c8, env=0xfffffff5d8) at dl-init.c:120
#5 0x000000fff7fca450 in _dl_start_user () from /lib64/ld.so.1
Backtrace stopped: frame did not save the PC
It seems that binutils generate bad shared lib.
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
--
YunQiang Su
Reply to: