[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#207167: marked as done (glibc: profiling threads gives wrong results)

Your message dated Sun, 13 Mar 2016 16:13:13 +0100
with message-id <20160313151313.GA25567@aurel32.net>
and subject line Re: Bug#207167: glibc: profiling threads gives wrong results
has caused the Debian Bug report #207167,
regarding glibc: profiling threads gives wrong results
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 owner@bugs.debian.org
immediately.)


-- 
207167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=207167
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: glibc
Version: unavailable; reported 2003-08-25
Severity: normal

When profiling threads, gprof actually only profiles the main thread,
which is quite useless. The reason is that there is only one timer for
the profiling, and that belongs to the main thread. In the profiling
case, each thread needs its own timer.

There are several solutions for this, such as a wrapper as on
  http://sam.zoy.org/writings/programming/gprof.html
This, however, is unsatisfactory. Compiling with "-p" should
automatically generate code like that or link code like that; for
instance with a weak pthread_create symbol. Of course that requires
interaction with GCC, but the important change is in the C library.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux kosh 2.4.21-2-k7 #1 Sat Jul 5 03:47:02 EST 2003 i686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8


-- 
|=| Michael Piefel
|=| Humboldt-Universität zu Berlin
|=| Tel. (+49 30) 2093 3831

--- End Message ---
--- Begin Message --- 
Version: 2.19-12

On 2003-08-27 09:44, GOTO Masanori wrote:
> At Mon, 25 Aug 2003 16:42:57 +0200,
> Michael Piefel wrote:
> > When profiling threads, gprof actually only profiles the main thread,
> > which is quite useless. The reason is that there is only one timer for
> > the profiling, and that belongs to the main thread. In the profiling
> > case, each thread needs its own timer.
> > 
> > There are several solutions for this, such as a wrapper as on
> >   http://sam.zoy.org/writings/programming/gprof.html
> > This, however, is unsatisfactory. Compiling with "-p" should
> > automatically generate code like that or link code like that; for
> > instance with a weak pthread_create symbol. Of course that requires
> > interaction with GCC, but the important change is in the C library.
> 
> Yes, it's long time concerned item, and not fixed.  I didn't know why
> Uli did not want to accept this kind of issue.  IMHO, we have a chance
> to investigate more when we support NPTL.

We have removed gprof support in libc6 in version 2.19-12 as there are
other ways of doing profiling nowadays. I am therefore closing this bug.

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: