[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#645058: marked as done (libc6: sh4: multiarch broken sometime)

Your message dated Sat, 10 Dec 2011 10:17:31 +0900
with message-id <CABMQnVKw2FcLFozm3Oa=o1tCooX7hmMyfwj9K=dmoPOyuwdjzA@mail.gmail.com>
and subject line Re: Bug#645058: libc6: sh4: multiarch broken sometime
has caused the Debian Bug report #645058,
regarding libc6: sh4: multiarch broken sometime
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 owner@bugs.debian.org
immediately.)


-- 
645058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645058
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6
Version: 2.13-21
Severity: important
User: multiarch-devel@lists.alioth.debian.org
Usertags: multiarch
User: debian-sh4@superh.org
Usertags: sh4
X-Debbugs-CC: debian-superh@lists.debian.org

Hi,

It seems to sh4 that multi-arch has broken.
A problem sometimes occurs by the library corresponding to multi-arch.

For example, A problem occurs in libmpc2_0.9-4 corresponding to multiarch.
A problem does not occur in old  libmpc2_0.9-3.

-----
$ /usr/lib/gcc/sh4-linux-gnu/4.6.1/cc1
$ dpkg -l | grep  libmpc2
ii  libmpc2                              0.9-3
multiple precision complex floating-point library
$ /usr/lib/gcc/sh4-linux-gnu/4.6.1/cc1
Segmentation fault (core dumped)
$ dpkg -l | grep  libmpc2
ii  libmpc2                              0.9-4
multiple precision complex floating-point library
$ gdb /usr/lib/gcc/sh4-linux-gnu/4.6.1/cc1 core
GNU gdb (GDB) 7.1-debian
Copyright (C) 2010 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 "sh4-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/lib/gcc/sh4-linux-gnu/4.6/cc1...(no
debugging symbols found)...done.
[New Thread 19413]

warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/sh4-linux-gnu/libmpc.so.2...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/sh4-linux-gnu/libmpc.so.2
Reading symbols from /usr/lib/sh4-linux-gnu/libmpfr.so.4...Reading
symbols from /usr/lib/debug/usr/lib/sh4-linux-gnu/libmpfr.so.4.1.0...done.
done.
Loaded symbols for /usr/lib/sh4-linux-gnu/libmpfr.so.4
Reading symbols from /usr/lib/sh4-linux-gnu/libgmp.so.10...(no
debugging symbols found)...done.
Loaded symbols for /usr/lib/sh4-linux-gnu/libgmp.so.10
Reading symbols from /lib/sh4-linux-gnu/libdl.so.2...(no debugging
symbols found)...done.
Loaded symbols for /lib/sh4-linux-gnu/libdl.so.2
Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/sh4-linux-gnu/libc.so.6...(no debugging
symbols found)...done.
Loaded symbols for /lib/sh4-linux-gnu/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Got object file from memory but can't read symbols: File format not recognized.
Core was generated by `/usr/lib/gcc/sh4-linux-gnu/4.6.1/cc1'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000000 in ?? ()
(gdb) info sharedlibrary
>From        To          Syms Read   Shared Object Library
0x295adfa0  0x295bbdc0  Yes (*)     /usr/lib/sh4-linux-gnu/libmpc.so.2
0x295d73a0  0x2965b740  Yes         /usr/lib/sh4-linux-gnu/libmpfr.so.4
0x296788e0  0x296c8840  Yes (*)     /usr/lib/sh4-linux-gnu/libgmp.so.10
0x296e2be0  0x296e3da0  Yes (*)     /lib/sh4-linux-gnu/libdl.so.2
0x296f7ac0  0x297056a0  Yes (*)     /usr/lib/libz.so.1
0x29730d20  0x29837800  Yes (*)     /lib/sh4-linux-gnu/libc.so.6
0x29556900  0x2956eea8  Yes (*)     /lib/ld-linux.so.2
(*): Shared library is missing debugging information.
(gdb) where
#0  0x00000000 in ?? ()
#1  0x296e299c in ?? () from /lib/sh4-linux-gnu/libdl.so.2
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
-----

It seems that the allocation is not operating normally.....

Best regards,
 Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

--- End Message ---
--- Begin Message --- 
Package: libc6
Version: 2.13-21

Hi,

The library where transition of libc has not completed the cause of
this problem was the cause.
It is not a problem of libc.
I close this bug.

Best regards,
  Nobuhiro

2011/12/10 Aurelien Jarno <aurelien@aurel32.net>:
> On Mon, Oct 17, 2011 at 02:03:51PM +0900, Nobuhiro Iwamatsu wrote:
>> Hi,
>>
>> 2011/10/12 Aurelien Jarno <aurelien@aurel32.net>:
>> > On Wed, Oct 12, 2011 at 03:28:19PM +0900, Nobuhiro Iwamatsu wrote:
>> >> Package: libc6
>> >> Version: 2.13-21
>> >> Severity: important
>> >> User: multiarch-devel@lists.alioth.debian.org
>> >> Usertags: multiarch
>> >> User: debian-sh4@superh.org
>> >> Usertags: sh4
>> >> X-Debbugs-CC: debian-superh@lists.debian.org
>> >>
>> >> Hi,
>> >>
>> >> It seems to sh4 that multi-arch has broken.
>> >> A problem sometimes occurs by the library corresponding to multi-arch.
>> >>
>> >> For example, A problem occurs in libmpc2_0.9-4 corresponding to multiarch.
>> >> A problem does not occur in old  libmpc2_0.9-3.
>> >>
>> >
>> > Have you tried to use libmpc2_0.9-3 manually moving the files to the
>> > multiarch path
>>
>> This work.
>>
>> > or libmpc2_0.9-4 manually moving the files to the
>> > non-multiarch path?
>>
>> This does not work.
>>
>> I understood that this was not a problem of multiarch. Sorry.
>>
>> >
>> > Besides the multiarch path, the other big difference between versions
>> > 0.9-3 and 0.9-4 is the use of CFLAGS, which means it has been built with
>> > something like:
>> >
>> > CFLAGS   = -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security
>> > CPPFLAGS =
>> > CXXFLAGS = -g -O2 -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security
>> > FFLAGS   = -g -O2
>> > LDFLAGS  = -Wl,-z,relro
>>
>> I built a package with CFLAGS as only "-g - O2 ". However, the problem
>> was not settled.
>> Other libraries may be related.
>>
>
> Any news on that?
>
> --
> Aurelien Jarno                          GPG: 1024D/F1BCDB73
> aurelien@aurel32.net                 http://www.aurel32.net



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6

--- End Message ---
Reply to: