Package: ltrace Version: 0.5-3.1 Severity: normal [...@satoko bd] ltrace /bin/true unexpected breakpoint at 0xf7e01d0f unexpected breakpoint at 0xf7df453f unexpected breakpoint at 0xf7df843f unexpected breakpoint at 0x8049f4f unexpected breakpoint at 0xf7e3b07f unexpected breakpoint at 0xf7e3111f unexpected breakpoint at 0xf7f3c42f +++ exited (status 0) +++
As you can see, even with /bin/true, ltrace fails to provide any useful output. I am running an x86_64 paravirtualized kernel (2.6.28 from kernel.org) with i386 userland under Xen. If the kernel is 32-bit, or is using the old xen stack (2.6.18 with the xen patches) the problem does not occur. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 2.6.28-cfg1 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ltrace depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libelfg0 0.8.10-2 an ELF object file access library ltrace recommends no packages. ltrace 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
