Your message dated Thu, 2 Jan 2014 16:01:33 +0100
with message-id <[email protected]>
and subject line fixed in 0.5.3-2.1
has caused the Debian Bug report #513965,
regarding ltrace fails under 64-bit pv_ops xen kernels w/32-bit userspace
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.)
--
513965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513965
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ltrace
Version: 0.5-3.1
Severity: normal
[bd@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
--- End Message ---
--- Begin Message ---
Version: 0.5.3-2.1
This bug is fixed since (at least) version 0.5.3-2.1
Thanks for your report,
--
Juan Cespedes
Debian Developer
--- End Message ---
