Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2012-06-16 Thread Pierre Chifflier 
Hi,

I have merged the patch from Alban Browaeys (thanks to him for writing
it) in version 0.6.6-2, just uploaded a few moments ago.

Thanks,
Pierre



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2012-05-28 Thread Alban Browaeys 
Package: libcap-ng0
Version: 0.6.6-1
Followup-For: Bug #631807

memset usage to reset the structure to 0 and NULL  is indeed the
culprit.
Here is a patch that fix the bug.
I made it after reading:
http://ex-parrot.com/~chris/random/initialise.html
as I clued that being pedantic could help and it did.
Sadly I found no pointer telling about the rationale for why only on armel
does it fail.
Thus all I can tell here is the memset hack breaks on an address-of on a no 
basic
type field of a __thread structure.

The patch is against src/cap-ng.c from libcap-ng 0.6.6
I tested the libcap-ng-utils on armel and also reinstalled bluez without
issues.

BR,
Alban


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4.0test0-03166-gf6a26ae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libcap-ng0 depends on:
ii  libc6  2.13-32

libcap-ng0 recommends no packages.

libcap-ng0 suggests no packages.

-- no debconf information
--- cap-ng.c.nofix	2012-05-29 04:35:34.0 +
+++ cap-ng.c.fix	2012-05-29 04:35:22.0 +
@@ -136,6 +136,11 @@
 	__u32 bounds[2];
 };
 
+
+static struct __user_cap_header_struct hdrzz = {0, 0};
+static cap_data_t datazz = { {0, 0, 0} };
+static __u32 boundzz = {0};
+
 // Global variables with per thread uniqueness
 static __thread struct cap_ng m =	{ 1,
 	{0, 0},
@@ -149,7 +154,7 @@
 	if (m.state != CAPNG_NEW)
 		return;
 
-	memset(m.hdr, 0, sizeof(m.hdr));
+	m.hdr = hdrzz;
 	(void)capget(m.hdr, NULL); // Returns -EINVAL
 	if (m.hdr.version == _LINUX_CAPABILITY_VERSION_3 ||
 		m.hdr.version == _LINUX_CAPABILITY_VERSION_2) {
@@ -161,7 +166,7 @@
 		return;
 	}
 
-	memset(m.data, 0, sizeof(cap_data_t));
+	m.data = datazz;
 #ifdef HAVE_SYSCALL_H
 	m.hdr.pid = (unsigned)syscall(__NR_gettid);
 #else
@@ -178,10 +183,13 @@
 		return;
 
 	if (set  CAPNG_SELECT_CAPS)
-		memset(m.data, 0, sizeof(cap_data_t));
+		m.data = datazz;
 #ifdef PR_CAPBSET_DROP
-	if (set  CAPNG_SELECT_BOUNDS)
-		memset(m.bounds, 0, sizeof(m.bounds));
+	if (set  CAPNG_SELECT_BOUNDS) {
+		unsigned i;
+		for (i=0; isizeof(m.bounds)/sizeof(__u32); i++)
+			m.bounds[i] = boundzz;
+	}
 #endif
 	m.state = CAPNG_INIT;
 }

Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2012-02-28 Thread Sascha Silbe 
Package: libcap-ng0
Version: 0.6.6-1
Followup-For: Bug #631807

Dear Maintainer,

I'm afraid I can also confirm this bug. Took me some time to realise
that it's not gnome-keyring-daemon's fault that it crashes (with a
segfault) on every invocation, even --help.

Fortunately, as Thomas Maass helpfully pointed out, the Ubuntu version
(0.6.6-1ubuntu1) does not exhibit the same problem, so I finally have a
workaround.

Still, it's a grave bug (at least on armel) that should be fixed ASAP
as it renders packages that link against libcap-ng0 completely
inoperable. (Sorry to not dig into it myself and send a patch, but I
already have my own fair share of bugs to fix.)

FWIW, this is on an XO-1.75 laptop [1].


[1] http://wiki.laptop.org/go/XO-1.75

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (1, 'experimental')
Architecture: armel (armv7l)

Kernel: Linux 3.0.0-mimosa-1-00214-gd1fa5f2 (PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libcap-ng0 depends on:
ii  libc6  2.13-26

libcap-ng0 recommends no packages.

libcap-ng0 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2012-02-03 Thread Thomas Maass 
Package: libcap-ng0
Version: 0.6.6-1
Followup-For: Bug #631807

I can confirm this bug. I took the ubuntu package as workaround.
http://ports.ubuntu.com/ubuntu-ports/pool/main/libc/libcap-ng/
The bug does not exist there.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: armel (armv7l)

Kernel: Linux 3.0.8-1-ac100 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libcap-ng0 depends on:
ii  libc6  2.13-24

libcap-ng0 recommends no packages.

libcap-ng0 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2011-11-04 Thread Alban Browaeys 
Package: libcap-ng0
Version: 0.6.6-1
Followup-For: Bug #631807

This time I rebuild the package libcap-ng vanilla (ie without
any tweaks) on the freerunner and it worked.

One diff with
https://buildd.debian.org/status/fetch.php?pkg=libcap-ngarch=armelver=0.6.6-1stamp=1309007854
is that I do not have those errors:
make[2]: Entering directory 
`/build/buildd-libcap-ng_0.6.6-1-armel-XxXlKD/libcap-ng-0.6.6/src'
/bin/bash ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I. 
-I..   -fPIC -DPIC -W -Wall -Wshadow -Wformat -Wundef -D_GNU_SOURCE -g -O2 -O0 
-MT cap-ng.lo -MD -MP -MF .deps/cap-ng.Tpo -c -o cap-ng.lo cap-ng.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I. -I.. -fPIC -DPIC -W -Wall 
-Wshadow -Wformat -Wundef -D_GNU_SOURCE -g -O2 -O0 -MT cap-ng.lo -MD -MP -MF 
.deps/cap-ng.Tpo -c cap-ng.c  -fPIC -DPIC -o .libs/cap-ng.o
cap-ng.c: In function 'get_bounding_set':
cap-ng.c:236:70: warning: signed and unsigned type in conditional expression 
[-Wsign-compare]
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I. -I.. -fPIC -DPIC -W -Wall 
-Wshadow -Wformat -Wundef -D_GNU_SOURCE -g -O2 -O0 -MT cap-ng.lo -MD -MP -MF 
.deps/cap-ng.Tpo -c cap-ng.c -o cap-ng.o /dev/null 21
mv -f .deps/cap-ng.Tpo .deps/cap-ng.Plo
/bin/bash ../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I. 
-I..   -fPIC -DPIC -W -Wall -Wshadow -Wformat -Wundef -D_GNU_SOURCE -g -O2 -O0 
-MT lookup_table.lo -MD -MP -MF .deps/lookup_table.Tpo -c -o lookup_table.lo 
lookup_table.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I. -I.. -fPIC -DPIC -W -Wall 
-Wshadow -Wformat -Wundef -D_GNU_SOURCE -g -O2 -O0 -MT lookup_table.lo -MD -MP 
-MF .deps/lookup_table.Tpo -c lookup_table.c  -fPIC -DPIC -o 
.libs/lookup_table.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I. -I.. -fPIC -DPIC -W -Wall 
-Wshadow -Wformat -Wundef -D_GNU_SOURCE -g -O2 -O0 -MT lookup_table.lo -MD -MP 
-MF .deps/lookup_table.Tpo -c lookup_table.c -o lookup_table.o /dev/null 21
mv -f .deps/lookup_table.Tpo .deps/lookup_table.Plo
/bin/bash ../libtool --tag=CC   --mode=link gcc -fPIC -DPIC -W -Wall -Wshadow 
-Wformat -Wundef -D_GNU_SOURCE -g -O2 -O0 -Wl,-z,relro -Wl,-z,defs -o 
libcap-ng.la -rpath /usr/lib cap-ng.lo lookup_table.lo  
libtool: link: gcc -shared  .libs/cap-ng.o .libs/lookup_table.o-Wl,-z 
-Wl,relro -Wl,-z -Wl,defs   -Wl,-soname -Wl,libcap-ng.so.0 -o 
.libs/libcap-ng.so.0.0.0
/usr/bin/ld.bfd.real: .libs/cap-ng.o(.text+0x1dc): R_ARM_REL32 used with TLS 
symbol m
/usr/bin/ld.bfd.real: .libs/cap-ng.o(.text+0x208): R_ARM_REL32 used with TLS 
symbol m
/usr/bin/ld.bfd.real: .libs/cap-ng.o(.text+0x32c): R_ARM_REL32 used with TLS 
symbol m
/usr/bin/ld.bfd.real: .libs/cap-ng.o(.text+0x330): R_ARM_REL32 used with TLS 
symbol m
libtool: link: (cd .libs  rm -f libcap-ng.so.0  ln -s 
libcap-ng.so.0.0.0 libcap-ng.so.0

ie R_ARM_REL32 used with TLS symbol m .

Sorry for the lag
Alban

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0test0 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libcap-ng0 depends on:
ii  libc6  2.13-21

libcap-ng0 recommends no packages.

libcap-ng0 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2011-08-24 Thread Timo Juhani Lindfors 
Hi,

I can reproduce this on my freerunner.

lindi@ginger:~$ sudo /etc/init.d/bluetooth start
Starting bluetooth:Segmentation fault
lindi@ginger:~$ dpkg-query -W|grep blue
bluez   4.94-3
bluez-hcidump   2.1-1
libbluetooth3   4.94-3
lindi@ginger:~$ dpkg-query -W|grep libc6
libc6   2.13-17
libc6-dev   2.13-17

-Timo



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2011-08-04 Thread Pierre Chifflier 
On Mon, Jun 27, 2011 at 03:00:37PM +0200, Alban Browaeys wrote:
 Hi,
 
 One important change I made to the 0.6.6 packages is that I enabled the
 hardening wrapper, which adds some flags to the compiler.
 
 Could you test if the problem is related to the optimization (as in
 #546823),
 or if commenting the line
 export DEB_BUILD_HARDENING=1
 on top of debian/rules solves the problem ?
 
 Thanks,
 Pierre
 
 
 My findings:
 Removing hardening or playing with cflags do not remove segfault.
 The way I managed to fix it is by removing the custom ldflags in
 debian/rules (it works
 even after I removed the ifeq that disables optimization on armel).

Hi,

You mean removing the LDFLAGS=-Wl,-z,defs part ? Or also the
PYFLAGS=... tweak for the Python modules too ?

BR,
Pierre



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2011-06-27 Thread Alban Browaeys 

Package: libcap-ng0
Version: 0.6.6-1
Severity: important

The issue about memset is back . I used gcc-4.6.real (Debian 4.6.0-14) 4.6.1 
20110616 (prerelease).
I rebuild the package locally first with dpkg-buildpackage -rfakeroot -b -uc 
-us then make; make install
to get the debugging symbols (using the previous debian generated makefiles).

filecap backtrace:
eading symbols from /usr/bin/filecap...done.
(gdb) r
Starting program: /usr/bin/filecap 

Program received signal SIGSEGV, Segmentation fault.
0x40039f78 in init () at cap-ng.c:152
152 memset(m.hdr, 0, sizeof(m.hdr));
(gdb) bt full
#0  0x40039f78 in init () at cap-ng.c:152
No locals.
#1  0x4003a18c in capng_clear (set=CAPNG_SELECT_BOTH) at cap-ng.c:176
No locals.
#2  0x4ba8 in check_file (fpath=0x40171050 /usr/sbin/NetworkManager, 
sb=0xbeffe4d0, typeflag_unused=0, s_unused=0xbefff62c) at filecap.c:56
rc = 36553
fd = 6
#3  0x400faed8 in process_entry (data=0xbefff618, dir=0xbeffe57c, 
name=0x401720b3 NetworkManager, namlen=value optimized out, d_type=8)
at ftw.c:470
st = {st_dev = 45857, __pad1 = 0, st_ino = 36553, st_mode = 33261, 
st_nlink = 1, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, 
  st_size = 718376, st_blksize = 4096, st_blocks = 1408, st_atim = 
{tv_sec = 1309057780, tv_nsec = 380737313}, st_mtim = {
tv_sec = 1306726376, tv_nsec = 0}, st_ctim = {tv_sec = 1309055517, 
tv_nsec = 529174812}, __unused4 = 0, __unused5 = 0}
result = value optimized out
flag = value optimized out
new_buflen = value optimized out
statres = value optimized out
#4  0x400fb1ec in ftw_dir (data=0xbefff618, st=value optimized out, 
old_dir=value optimized out) at ftw.c:546
dir = {stream = 0x40172058, streamfd = 5, content = 0x0}
d = 0x401720a0
previous_base = 5
result = 0
startp = value optimized out
__PRETTY_FUNCTION__ = ftw_dir
#5  0x400fb950 in ftw_startup (dir=value optimized out, is_nftw=value 
optimized out, func=value optimized out, 
descriptors=value optimized out, flags=1) at ftw.c:772
name = 0x40171050 /usr/sbin/NetworkManager
data = {dirstreams = 0xbeffe5b0, actdir = 1, maxdir = 1024, dirbuf = 
0x40171050 /usr/sbin/NetworkManager, dirbufsize = 4096, ftw = {
base = 10, level = 1}, flags = 1, cvt_arr = 0x4015340c, func = 
0x4b4c check_file, dev = 45857, known_objects = 0x0}
st = {st_dev = 45857, __pad1 = 0, st_ino = 175, st_mode = 16877, 
st_nlink = 2, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, 
  st_size = 12288, st_blksize = 4096, st_blocks = 24, st_atim = {tv_sec 
= 1309059829, tv_nsec = 693237324}, st_mtim = {
tv_sec = 1309057020, tv_nsec = 388549812}, st_ctim = {tv_sec = 
1309057020, tv_nsec = 388549812}, __unused4 = 0, __unused5 = 0}
result = 1075253328
cwdfd = value optimized out
cwd = 0x0
cp = value optimized out
---Type return to continue, or q return to quit---
#6  0x400fbaa8 in __new_nftw (path=0x400238c8 \001, func=value optimized 
out, descriptors=0, flags=1073889224) at ftw.c:856
No locals.
#7  0x4000106c in main (argc=1, argv=0xbefff864) at filecap.c:154
path_env = 0xbe2a 
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
path = 0x40171008 /usr/local/sbin
dir = 0x40171027 /usr/sbin
sbuf = {st_dev = 0, __pad1 = 36800, st_ino = 1073909688, st_mode = 0, 
st_nlink = 1073909712, st_uid = 0, st_gid = 0, st_rdev = 0, 
  __pad2 = 0, st_size = 0, st_blksize = 0, st_blocks = 0, st_atim = 
{tv_sec = 0, tv_nsec = 1073909704}, st_mtim = {tv_sec = 0, 
tv_nsec = 0}, st_ctim = {tv_sec = 0, tv_nsec = 0}, __unused4 = 0, 
__unused5 = 0}
nftw_flags = 1
i = 1073746516


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: armel (armv7l)

Kernel: Linux 3.0.0-rc4-a101-initramfs-11146-ga699455-dirty (PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libcap-ng0 depends on:
ii  libc6 2.13-7 Embedded GNU C Library: Shared lib

libcap-ng0 recommends no packages.

libcap-ng0 suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2011-06-27 Thread Pierre Chifflier 
On Mon, Jun 27, 2011 at 01:44:01PM +0200, Alban Browaeys wrote:
 
 Package: libcap-ng0
 Version: 0.6.6-1
 Severity: important
 
 The issue about memset is back . I used gcc-4.6.real (Debian 4.6.0-14) 4.6.1 
 20110616 (prerelease).
 I rebuild the package locally first with dpkg-buildpackage -rfakeroot -b -uc 
 -us then make; make install
 to get the debugging symbols (using the previous debian generated makefiles).

Hi,

One important change I made to the 0.6.6 packages is that I enabled the
hardening wrapper, which adds some flags to the compiler.

Could you test if the problem is related to the optimization (as in
#546823),
or if commenting the line
export DEB_BUILD_HARDENING=1
on top of debian/rules solves the problem ?

Thanks,
Pierre

 
 filecap backtrace:
 eading symbols from /usr/bin/filecap...done.
 (gdb) r
 Starting program: /usr/bin/filecap 
 
 Program received signal SIGSEGV, Segmentation fault.
 0x40039f78 in init () at cap-ng.c:152
 152   memset(m.hdr, 0, sizeof(m.hdr));
 (gdb) bt full
 #0  0x40039f78 in init () at cap-ng.c:152
 No locals.
 #1  0x4003a18c in capng_clear (set=CAPNG_SELECT_BOTH) at cap-ng.c:176
 No locals.
 #2  0x4ba8 in check_file (fpath=0x40171050 /usr/sbin/NetworkManager, 
 sb=0xbeffe4d0, typeflag_unused=0, s_unused=0xbefff62c) at filecap.c:56
 rc = 36553
 fd = 6
 #3  0x400faed8 in process_entry (data=0xbefff618, dir=0xbeffe57c, 
 name=0x401720b3 NetworkManager, namlen=value optimized out, d_type=8)
 at ftw.c:470
 st = {st_dev = 45857, __pad1 = 0, st_ino = 36553, st_mode = 33261, 
 st_nlink = 1, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, 
   st_size = 718376, st_blksize = 4096, st_blocks = 1408, st_atim = 
 {tv_sec = 1309057780, tv_nsec = 380737313}, st_mtim = {
 tv_sec = 1306726376, tv_nsec = 0}, st_ctim = {tv_sec = 
 1309055517, tv_nsec = 529174812}, __unused4 = 0, __unused5 = 0}
 result = value optimized out
 flag = value optimized out
 new_buflen = value optimized out
 statres = value optimized out
 #4  0x400fb1ec in ftw_dir (data=0xbefff618, st=value optimized out, 
 old_dir=value optimized out) at ftw.c:546
 dir = {stream = 0x40172058, streamfd = 5, content = 0x0}
 d = 0x401720a0
 previous_base = 5
 result = 0
 startp = value optimized out
 __PRETTY_FUNCTION__ = ftw_dir
 #5  0x400fb950 in ftw_startup (dir=value optimized out, is_nftw=value 
 optimized out, func=value optimized out, 
 descriptors=value optimized out, flags=1) at ftw.c:772
 name = 0x40171050 /usr/sbin/NetworkManager
 data = {dirstreams = 0xbeffe5b0, actdir = 1, maxdir = 1024, dirbuf = 
 0x40171050 /usr/sbin/NetworkManager, dirbufsize = 4096, ftw = {
 base = 10, level = 1}, flags = 1, cvt_arr = 0x4015340c, func = 
 0x4b4c check_file, dev = 45857, known_objects = 0x0}
 st = {st_dev = 45857, __pad1 = 0, st_ino = 175, st_mode = 16877, 
 st_nlink = 2, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, 
   st_size = 12288, st_blksize = 4096, st_blocks = 24, st_atim = 
 {tv_sec = 1309059829, tv_nsec = 693237324}, st_mtim = {
 tv_sec = 1309057020, tv_nsec = 388549812}, st_ctim = {tv_sec = 
 1309057020, tv_nsec = 388549812}, __unused4 = 0, __unused5 = 0}
 result = 1075253328
 cwdfd = value optimized out
 cwd = 0x0
 cp = value optimized out
 ---Type return to continue, or q return to quit---
 #6  0x400fbaa8 in __new_nftw (path=0x400238c8 \001, func=value optimized 
 out, descriptors=0, flags=1073889224) at ftw.c:856
 No locals.
 #7  0x4000106c in main (argc=1, argv=0xbefff864) at filecap.c:154
 path_env = 0xbe2a 
 /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 path = 0x40171008 /usr/local/sbin
 dir = 0x40171027 /usr/sbin
 sbuf = {st_dev = 0, __pad1 = 36800, st_ino = 1073909688, st_mode = 0, 
 st_nlink = 1073909712, st_uid = 0, st_gid = 0, st_rdev = 0, 
   __pad2 = 0, st_size = 0, st_blksize = 0, st_blocks = 0, st_atim = 
 {tv_sec = 0, tv_nsec = 1073909704}, st_mtim = {tv_sec = 0, 
 tv_nsec = 0}, st_ctim = {tv_sec = 0, tv_nsec = 0}, __unused4 = 0, 
 __unused5 = 0}
 nftw_flags = 1
 i = 1073746516
 
 
 -- System Information:
 Debian Release: wheezy/sid
   APT prefers unstable
   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
 Architecture: armel (armv7l)
 
 Kernel: Linux 3.0.0-rc4-a101-initramfs-11146-ga699455-dirty (PREEMPT)
 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash
 
 Versions of packages libcap-ng0 depends on:
 ii  libc6 2.13-7 Embedded GNU C Library: Shared 
 lib
 
 libcap-ng0 recommends no packages.
 
 libcap-ng0 suggests no packages.
 
 -- no debconf information
 
 
 



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?

Bug#631807: segfault in libcap-ng0 is back on armel - filecap , bluetoothd etc

2011-06-27 Thread Alban Browaeys 

Hi,

One important change I made to the 0.6.6 packages is that I enabled the
hardening wrapper, which adds some flags to the compiler.

Could you test if the problem is related to the optimization (as in
#546823),
or if commenting the line
export DEB_BUILD_HARDENING=1
on top of debian/rules solves the problem ?

Thanks,
Pierre



My findings:
Removing hardening or playing with cflags do not remove segfault.
The way I managed to fix it is by removing the custom ldflags in 
debian/rules (it works

even after I removed the ifeq that disables optimization on armel).

BR,
Alban 




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org