RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

A binary compiled with "-pg" doesn't produce any profiling information (no gmon.out). The application start with an error message.

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

Name        : glibc
Version     : 2.17
Release     : 103.el7
Architecture: ppc64le

How reproducible:

Every time

Steps to Reproduce:
1. Create a a basic C file:

#include <stdio.h>
int main(void)
{
    printf("Hello World\n");
    return 0;
}
2. Compile: gcc -o hello -pg hello.c
3. Run:
$ ./hello
monstartup: out of memory
Hello World
$ ls gmon.out
ls: cannot access gmon.out: No such file or directory

Actual results:

Error at starting.
No gmon.out file

Expected results:

No error.
A gmon.out file to use.

Additional info:

According to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1402726
This bug is fixed upstream by:
https://sourceware.org/git/?p=glibc.git;a=commit;h=a53fbd8e6cd2f69bdfa3431d616a5f332aea6664

Thanks for the bug and the reference to the upstream commit.

We are outside of the RHEL 7.2 development window right now, so we are considering this for RHEL 7.3.

*** Bug 1290414 has been marked as a duplicate of this bug. ***

Hello,
This bug has been copied as 7.2 z-stream (EUS) bug #1298930

Thank You
Joe Kachuck

(In reply to Joseph Kachuck from comment #18)
> Hello,
> This bug has been copied as 7.2 z-stream (EUS) bug #1298930
> 
> Thank You
> Joe Kachuck
.
... I think this has to read "... bug #1298956 ..." ... 
... please confirm or advise ...

Hello,
Yes I apologize that was a typo:
 This bug has been copied as 7.2 z-stream (EUS) bug #1298956

Thank You
Joe Kachuck

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2016-2573.html