Bug 409571 - [4.6][gcore] When the gcore command is executed, it takes a really long time.
Summary: [4.6][gcore] When the gcore command is executed, it takes a really long time.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gdb
Version: 4.6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jan Kratochvil
QA Contact:
URL:
Whiteboard:
Depends On: 408661
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-03 22:39 UTC by Jan Kratochvil
Modified: 2008-07-24 19:56 UTC (History)
1 user (show)

Fixed In Version: RHBA-2008-0717
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-24 19:56:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
.c file with 2GB .bss (90 bytes, text/plain)
2007-12-03 22:39 UTC, Jan Kratochvil 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2008:0717 0 normal SHIPPED_LIVE gdb bug fix update 2008-07-23 16:16:02 UTC

Comment 1 Jan Kratochvil 2007-12-03 22:39:06 UTC 
Created attachment 276341 [details]
.c file with 2GB .bss
Comment 2 RHEL Program Management 2007-12-03 22:44:44 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 9 errata-xmlrpc 2008-07-24 19:56:49 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0717.html
Note You need to log in before you can comment on or make changes to this bug.