Bug 179829 - gstack doesn't run if PATH is broken
Summary: gstack doesn't run if PATH is broken
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gdb
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Alexandre Oliva
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks: 181409 190548
TreeView+ depends on / blocked
 
Reported: 2006-02-03 09:12 UTC by Bastien Nocera
Modified: 2015-01-08 00:11 UTC (History)
4 users (show)

Fixed In Version: RHBA-2006-0429
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-10 21:18:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
gstack-without-path.patch (988 bytes, patch)
2006-02-03 09:12 UTC, Bastien Nocera
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0429 0 normal SHIPPED_LIVE gdb bug fix update 2006-08-09 04:00:00 UTC

Description Bastien Nocera 2006-02-03 09:12:55 UTC
gdb-6.3.0.0-1.96

This would happen if the caller (in this case, a signal handler in Oracle)
doesn't set the environment properly.

Patch attached

Comment 1 Bastien Nocera 2006-02-03 09:12:56 UTC
Created attachment 124099 [details]
gstack-without-path.patch

Comment 8 Bob Johnson 2006-04-11 16:31:45 UTC
This issue is on Red Hat Engineering's list of planned work items 
for the upcoming Red Hat Enterprise Linux 4.4 release.  Engineering 
resources have been assigned and barring unforeseen circumstances, Red 
Hat intends to include this item in the 4.4 release.

Comment 13 Red Hat Bugzilla 2006-08-10 21:18:10 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 the 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-2006-0429.html



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