Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu

2010-06-06 Thread Aurelien Jarno
On Sun, Jun 06, 2010 at 11:40:26AM +0200, Gianluigi Tiesi wrote: Package: libc6-i686 Version: 2.11.1-2 Severity: serious Tags: sid I'm unable to run valgrind without renaming /lib/i686 it asserts on: .../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' I've

Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu

2010-06-06 Thread Gianluigi Tiesi
On 06/06/2010 13.21, Aurelien Jarno wrote: Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores) This part is not consistent. Are you running reportbug on a different machine? yes the problem is on a old amd 800mhz box, but I use a different box for submitting do you need some additional

Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu

2010-06-06 Thread Aurelien Jarno
On Sun, Jun 06, 2010 at 02:17:29PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 13.21, Aurelien Jarno wrote: Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores) This part is not consistent. Are you running reportbug on a different machine? yes the problem is on a old amd 800mhz

Bug#584607: libc6: autoconf configure scripts hang at checking whether a statically linked program can dlopen itself

2010-06-06 Thread Aurelien Jarno
reassign 584607 binutils-gold thanks On Sat, Jun 05, 2010 at 12:02:47AM -0300, Nicolás Alvarez wrote: On 6/4/10, Clint Adams sch...@debian.org wrote: On Fri, Jun 04, 2010 at 11:01:11PM -0300, Nicolás Alvarez wrote: gcc -o conftest -g -O2 -DHAVE_DLFCN_H -Wl,--export-dynamic -static

Processed: Re: Bug#584607: libc6: autoconf configure scripts hang at checking whether a statically linked program can dlopen itself

2010-06-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: reassign 584607 binutils-gold Bug #584607 [libc6] libc6: autoconf configure scripts hang at checking whether a statically linked program can dlopen itself Bug reassigned from package 'libc6' to 'binutils-gold'. Bug No longer marked as found in

Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu

2010-06-06 Thread Gianluigi Tiesi
On 06/06/2010 14.55, Aurelien Jarno wrote: On Sun, Jun 06, 2010 at 02:17:29PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 13.21, Aurelien Jarno wrote: Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores) This part is not consistent. Are you running reportbug on a different machine? yes

Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu

2010-06-06 Thread Aurelien Jarno
On Sun, Jun 06, 2010 at 10:27:12PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 14.55, Aurelien Jarno wrote: On Sun, Jun 06, 2010 at 02:17:29PM +0200, Gianluigi Tiesi wrote: On 06/06/2010 13.21, Aurelien Jarno wrote: Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/8 CPU cores) This part is not

Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu

2010-06-06 Thread Aurelien Jarno
On Sun, Jun 06, 2010 at 11:03:15PM +0200, Aurelien Jarno wrote: Unfortunately I am not able to reproduce it. Tried on an Athlon and on Opteron CPU. I am just wondering, what is the version of valgrind, and how exactly do you trigger the bug (valgrind command line, code, etc.) -- Aurelien

r4326 - in glibc-package/trunk/debian: . patches patches/hurd-i386 testsuite-checking

2010-06-06 Thread Samuel Thibault
Author: sthibault Date: 2010-06-06 22:21:17 + (Sun, 06 Jun 2010) New Revision: 4326 Added: glibc-package/trunk/debian/patches/hurd-i386/submitted-ttyname.diff Modified: glibc-package/trunk/debian/changelog glibc-package/trunk/debian/patches/series

Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu

2010-06-06 Thread Gianluigi Tiesi
On 06/06/2010 23.09, Aurelien Jarno wrote: On Sun, Jun 06, 2010 at 11:03:15PM +0200, Aurelien Jarno wrote: Unfortunately I am not able to reproduce it. Tried on an Athlon and on Opteron CPU. I am just wondering, what is the version of valgrind, and how exactly do you trigger the bug

Bug#584748: ../sysdeps/x86_64/cacheinfo.c:255: handle_intel: Assertion `maxidx = 2' on AMD cpu

2010-06-06 Thread Gianluigi Tiesi
On 06/06/2010 23.09, Aurelien Jarno wrote: On Sun, Jun 06, 2010 at 11:03:15PM +0200, Aurelien Jarno wrote: Unfortunately I am not able to reproduce it. Tried on an Athlon and on Opteron CPU. I am just wondering, what is the version of valgrind, and how exactly do you trigger the bug