Bug#385704: marked as done (libc6-dbg debug symbols cannot be parsed by oprpfile for some reason)
Your message dated Thu, 30 Aug 2007 22:18:42 +0900
with message-id <87odgpma8d.dancerj%dancer@netfort.gr.jp>
and subject line Bug#385704: follow-up on oprofile/libc6-dbg(amd64)
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: libc6-dbg debug symbols cannot be parsed by oprpfile for some reason
- From: Junichi Uekawa <dancer@netfort.gr.jp>
- Date: Sat, 02 Sep 2006 21:15:33 +0900
- Message-id: <87bqpyihwa.dancerj%dancer@netfort.gr.jp>
Package: libc6-dbg
Version: 2.3.6.ds1-4
opreport seems to be looking at the file (from strace):
open("/lib/tls/i686/cmov/libc-2.3.6.so", O_RDONLY) = 4
stat64("/lib/tls/i686/cmov/libc-2.3.6.so", {st_mode=S_IFREG|0755, st_size=1241580, ...}) = 0
open("/lib/tls/i686/cmov/libc-2.3.6.so", O_RDONLY|O_LARGEFILE) = 5
open("/lib/tls/i686/cmov/.debug/libc-2.3.6.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
open("/usr/lib/debug/lib/tls/i686/cmov/libc-2.3.6.so", O_RDONLY|O_LARGEFILE) = 5
but does not seem to be able to find the symbols there:
CPU: Core Solo / Duo, speed 1833 MHz (estimated)
Counted CPU_CLK_UNHALTED events (Unhalted clock cycles) with a unit mask of 0x00 (Unhalted core cycles) count 180000
samples % image name app name symbol name
321257 31.5939 processor.ko processor acpi_processor_idle
114285 11.2393 libc-2.3.6.so dpkg (no symbols)
67157 6.6045 libruby1.8.so.1.8.4 ruby1.8 (no symbols)
49197 4.8383 libc-2.3.6.so dpkg-query (no symbols)
How could I have a meaningful profile output?
regards,
junichi
--
dancer@{debian.org,netfort.gr.jp} Debian Project
--- End Message ---
--- Begin Message ---
Hi,
> >
> > I'm still seeing that oprofile cannot use libc6-dbg. Anyone seeing the same problem?
>
> it's an issue with oprofile that needs to be rebuilt and have a
> versionned dependency on recent binutils. There is an open RC bug about
> that, and if the maintainer does not fixes it, I'm going to NMU it as I
> say in the bugreport (the oprofile one).
>
> Note that it has nothing to do with the libc6-dbg issue amd64 (and
> other archs) had, it's an oprofile issue only.
Verified that this bug is fixed.
I tried with a locally-built oprofile new upstream version.
regards,
junichi
--
dancer@{debian.org,netfort.gr.jp} Debian Project
--- End Message ---
Reply to: