Bug 81609 - Profiling
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: glibc (Show other bugs)
ia64 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-01-10 20:59 EST by Thomas Cullison
Modified: 2007-11-30 17:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-28 02:38:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Thomas Cullison 2003-01-10 20:59:14 EST
Description of problem:
I tried to profile some code and ended up getting a core 
dump.  I did a bit
of looking at my code and decided to try the hello program 
and it had the
same problem.
I did a quick search on google and came up with the following 
link that
describes something similar.  I've included the patch.
> https://external-lists.vasoftware.com/archives/linux-ia64/2002

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 2 Jakub Jelinek 2003-01-20 13:06:56 EST
Do you have glibc-2.2.4-31.7 installed?
Comment 3 Thomas Cullison 2003-01-21 15:33:56 EST
No, glibc-2.2.4-29.2  is installed.  Is there a specific fix for this issue in 

Also, Can you remove the names (at least sirnames), and email address posted 
under the first 'Additional Comment'?
Comment 4 Thomas Cullison 2003-03-04 18:44:43 EST
I haven't received any updates on this issue.
Comment 5 Ulrich Drepper 2004-09-28 02:38:12 EDT
We don't break out patches.  If you want to do this, you are on your own.

I assume the current AS2.1 glibc works since I have not heard about
anybody having problems.

And no, we cannot change the text of comments.  All I can do is to
make it private which I'll do now.

Note You need to log in before you can comment on or make changes to this bug.