Your message dated Wed, 02 Mar 2011 15:17:41 +0000
with message-id <[email protected]>
and subject line Bug#611768: fixed in binutils 2.21.0.20110302-1
has caused the Debian Bug report #611768,
regarding binutils: [m68k] please apply relocation fix from upstream
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 [email protected]
immediately.)
--
611768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611768
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: binutils
Version: 2.20.1-16
Hi,
please apply the patch from Andreas Schwab to binutils:
http://sourceware.org/ml/binutils/2011-02/msg00008.html
This is supposed to fix a problem where a simple programme just
calling res_init() on m68k segfaults due to invalid memory access
apparently due to broken reloaction.
I’ve cited part of the mailing list thread below for reference.
Thanks in advance,
//mirabilos
--
I believe no one can invent an algorithm. One just happens to hit upon it
when God enlightens him. Or only God invents algorithms, we merely copy them.
If you don't believe in God, just consider God as Nature if you won't deny
existence. -- Coywolf Qi Hunt
---------- Forwarded message ----------
From: Thorsten Glaser <[email protected]>
Message-ID: <[email protected]>
To: [email protected]
Date: Sun, 30 Jan 2011 20:31:44 +0000 (UTC)
Subject: Re: [m68k] res_init segfault, need help debugging
Dixi quod…
>ara2:~# cat >x.c
>#include <netinet/in.h>
>#include <arpa/nameser.h>
>#include <resolv.h>
>
>int
>main(void)
>{
> return (res_init());
>}
>ara2:~# gcc x.c
>ara2:~# ./a.out
>Segmentation fault
>Basically, the segfault is on accessing _res.retrans
>in line 67 (first access of _res)
Now, _res is at 0xc014ce58 and the code in question is:
0xc00f1eb4 <__res_init>: linkw %fp,#0
0xc00f1eb8 <__res_init+4>: moveml %d2-%d5/%a2/%a5,%sp@-
0xc00f1ebc <__res_init+8>: lea %pc@(0xc0148000),%a5
0xc00f1ec4 <__res_init+16>: movel %a5,%d5
0xc00f1ec6 <__res_init+18>: addil #9916,%d5
0xc00f1ecc <__res_init+24>: movel %d5,%sp@-
0xc00f1ece <__res_init+26>: movel %d5,%sp@
0xc00f1ed0 <__res_init+28>: bsrl 0xc0040aa0 <__tls_get_addr@plt>
0xc00f1ed6 <__res_init+34>: addql #4,%sp
=> 0xc00f1ed8 <__res_init+36>: moveal %a0@,%a2
0xc00f1eda <__res_init+38>: tstl %a2@
0xc00f1edc <__res_init+40>: bnes 0xc00f1ee2 <__res_init+46>
0xc00f1ede <__res_init+42>: moveq #5,%d0
0xc00f1ee0 <__res_init+44>: movel %d0,%a2@
0xc00f1ee2 <__res_init+46>: tstl %a2@(4)
0xc00f1ee6 <__res_init+50>: bnes 0xc00f1eee <__res_init+58>
0xc00f1ee8 <__res_init+52>: moveq #4,%d1
0xc00f1eea <__res_init+54>: movel %d1,%a2@(4)
0xc00f1eee <__res_init+58>: btst #0,%a2@(11)
0xc00f1ef4 <__res_init+64>: bnes 0xc00f1f5a <__res_init+166>
The access happens with:
a0 0xc0021be1 0xc0021be1
a2 0x0 0x0
If I read that right, it’s the equivalent of: mov a2,dword ptr [a0]
So, question, why does that access out-of-bounds memory? This is
apparently introduced with TLS support.
(gdb) info sharedlibrary
From To Syms Read Shared Object Library
0xc00021d8 0xc00148b0 Yes /lib/ld.so.1
0xc0040adc 0xc011ba62 Yes /lib/libc.so.6
According to "info target" there’s nothing there:
[…]
0xc001d05c - 0xc001d120 is .bss in /lib/ld.so.1
0xc0022174 - 0xc0022198 is .note.gnu.build-id in /lib/libc.so.6
[…]
bye,
//mirabilos
--
22:20⎜<asarch> The crazy that persists in his craziness becomes a master
22:21⎜<asarch> And the distance between the craziness and geniality is
only measured by the success 22:21⎜<mksh> it’s a
very thin line anyway… with some, you don’t know which side they’re on
---------- Forwarded message ----------
From: Andreas Schwab <[email protected]>
Message-ID: <[email protected]>
Cc: [email protected]
Date: Tue, 01 Feb 2011 20:21:50 +0100
Subject: Re: [m68k] res_init segfault, need help debugging
It's a linker bug, see
<http://sourceware.org/ml/binutils/2011-02/msg00008.html>.
Andreas.
--
Andreas Schwab, [email protected]
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--- End Message ---
--- Begin Message ---
Source: binutils
Source-Version: 2.21.0.20110302-1
We believe that the bug you reported is fixed in the latest version of
binutils, which is due to be installed in the Debian FTP archive:
binutils-dev_2.21.0.20110302-1_amd64.deb
to main/b/binutils/binutils-dev_2.21.0.20110302-1_amd64.deb
binutils-doc_2.21.0.20110302-1_all.deb
to main/b/binutils/binutils-doc_2.21.0.20110302-1_all.deb
binutils-gold_2.21.0.20110302-1_amd64.deb
to main/b/binutils/binutils-gold_2.21.0.20110302-1_amd64.deb
binutils-multiarch_2.21.0.20110302-1_amd64.deb
to main/b/binutils/binutils-multiarch_2.21.0.20110302-1_amd64.deb
binutils-source_2.21.0.20110302-1_all.deb
to main/b/binutils/binutils-source_2.21.0.20110302-1_all.deb
binutils_2.21.0.20110302-1.diff.gz
to main/b/binutils/binutils_2.21.0.20110302-1.diff.gz
binutils_2.21.0.20110302-1.dsc
to main/b/binutils/binutils_2.21.0.20110302-1.dsc
binutils_2.21.0.20110302-1_amd64.deb
to main/b/binutils/binutils_2.21.0.20110302-1_amd64.deb
binutils_2.21.0.20110302.orig.tar.gz
to main/b/binutils/binutils_2.21.0.20110302.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose <[email protected]> (supplier of updated binutils package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 02 Mar 2011 02:41:17 +0100
Source: binutils
Binary: binutils binutils-dev binutils-multiarch binutils-gold binutils-hppa64
binutils-spu binutils-doc binutils-source
Architecture: source all amd64
Version: 2.21.0.20110302-1
Distribution: unstable
Urgency: low
Maintainer: Matthias Klose <[email protected]>
Changed-By: Matthias Klose <[email protected]>
Description:
binutils - The GNU assembler, linker and binary utilities
binutils-dev - The GNU binary utilities (BFD development files)
binutils-doc - Documentation for the GNU assembler, linker and binary utilities
binutils-gold - The (experimental) GNU gold linker utility
binutils-hppa64 - The GNU assembler, linker and binary utilities targeted for
hppa6
binutils-multiarch - Binary utilities that support multi-arch targets
binutils-source - The GNU assembler, linker and binary utilities (source)
binutils-spu - The GNU assembler, linker and binary utilities targeted for
spu-e
Closes: 611768
Changes:
binutils (2.21.0.20110302-1) unstable; urgency=low
.
* Update from the 2.21 branch.
.
[ Thorsten Glaser ]
* patches/640_m68k_fix-TLS_GD-relocation: new, temp. Closes: #611768.
.
[ Matthias Klose ]
* On ppc64, look for 32 bit target libraries in /lib32, /usr/lib32 etc.,
first.
Checksums-Sha1:
348efa5842ba15fefcb244865d0f4f4e93ddfa70 1483 binutils_2.21.0.20110302-1.dsc
d7189fabfeb3465e4f6a3da4fad66439865e9a1b 22777641
binutils_2.21.0.20110302.orig.tar.gz
90ceb5cb751c19f7cb2f5b1cc49ba928622e8a26 59367
binutils_2.21.0.20110302-1.diff.gz
7e5c47323341e06975d5432bb66496027156ba49 564198
binutils-doc_2.21.0.20110302-1_all.deb
43de1ee194cb9712e5a1fe781167c47128130726 13250404
binutils-source_2.21.0.20110302-1_all.deb
4aa5f15fd13453c6f094d62d2c433cd7c7b1d7e9 4545378
binutils_2.21.0.20110302-1_amd64.deb
a1e4e6c9c26d37198c4f98638a523efd53a6a5b1 3807772
binutils-dev_2.21.0.20110302-1_amd64.deb
2f2b0f98de197b974c70111e558d4991f0c13a54 2126744
binutils-multiarch_2.21.0.20110302-1_amd64.deb
97ebcfbe789484d90a5f407be19c006f383f7495 1400
binutils-gold_2.21.0.20110302-1_amd64.deb
Checksums-Sha256:
34082086d42c719308d38b9c2a6254f0f7a8ed85e43c876adcc120d77d460dcf 1483
binutils_2.21.0.20110302-1.dsc
610fe3a46b3a633106858c42e662f27e3d6131f911c979a95fda99c947b56144 22777641
binutils_2.21.0.20110302.orig.tar.gz
ca6358889f5e1af2b6ff95ebf1c573be5b03b24cc6a8e69612d2bee101070468 59367
binutils_2.21.0.20110302-1.diff.gz
ecba0c9011831b42909061e81e80aa15240109b5f0034529a3a46cb898c918ca 564198
binutils-doc_2.21.0.20110302-1_all.deb
df5461be9294d9571c9a7893fbe6a734e60482439632678c8db9a7fac9b3529b 13250404
binutils-source_2.21.0.20110302-1_all.deb
d93b19cc7d84f8c33c00b58e58d1c91b31653c95b6b7d54001e0881b59f11ee8 4545378
binutils_2.21.0.20110302-1_amd64.deb
2fa07fb5b60f3608cc1188507db9254783d741a094b24e418f069f007b7e76fb 3807772
binutils-dev_2.21.0.20110302-1_amd64.deb
f342a6f0e796092be85f80b5732edcf58b6691ba0cf89057d9032680631bb5b0 2126744
binutils-multiarch_2.21.0.20110302-1_amd64.deb
4f03cb01b8db861327232726aead93f1ce89f41ba16a227f66ddebb66fc7fbde 1400
binutils-gold_2.21.0.20110302-1_amd64.deb
Files:
e1a3737243ae6806c685dccffea9b0ec 1483 devel optional
binutils_2.21.0.20110302-1.dsc
ac3512de5ac2950121d6bdaa9c71184c 22777641 devel optional
binutils_2.21.0.20110302.orig.tar.gz
df83d473037492d85f337078dd6c05f4 59367 devel optional
binutils_2.21.0.20110302-1.diff.gz
1ce571b21b2ec70a062d72899b5af7a8 564198 doc optional
binutils-doc_2.21.0.20110302-1_all.deb
5811a7937af0dd3921347f3dfdcb6099 13250404 devel optional
binutils-source_2.21.0.20110302-1_all.deb
57fd20e1608ea6f712b0480d9b6889b1 4545378 devel optional
binutils_2.21.0.20110302-1_amd64.deb
8e4702a2b718eb1a57fefe44780e83e7 3807772 devel extra
binutils-dev_2.21.0.20110302-1_amd64.deb
019b22cbee5215d349cb442e473bcc47 2126744 devel extra
binutils-multiarch_2.21.0.20110302-1_amd64.deb
7f2cadd14aafd315631269f77c5289c5 1400 devel extra
binutils-gold_2.21.0.20110302-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAk1tp+0ACgkQStlRaw+TLJwSowCfdHUUsMeBCMkt3lFa5X/wVj2H
z4QAoKiIsIrwETFNGN3SIPFLAKH8faf+
=veXL
-----END PGP SIGNATURE-----
--- End Message ---
