Bug 410661 - add environment .note section to corefile
Summary: add environment .note section to corefile
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.1
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Neil Horman
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 173278
TreeView+ depends on / blocked
 
Reported: 2007-12-04 16:46 UTC by Andrew Cagney
Modified: 2009-04-17 11:02 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-17 11:02:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Cagney 2007-12-04 16:46:54 UTC
The environment passed into the core file is not available (in theory one could
groak it via the .auxv note section and memory but in reality it is corrupted).
 This makes actions such as correctly restarting a corefile impossible.

Suggest writing out the environement (environ[]) to a separate .note section.

Comment 1 Neil Horman 2008-08-05 16:30:58 UTC
with 5.3 you can use proc/sys/kernel/core_pattern to interrogate /proc/<pid>/environ to grab a crashing processes environment

Comment 2 Andrew Cagney 2008-08-11 14:15:46 UTC
(In reply to comment #1)
> with 5.3 you can use proc/sys/kernel/core_pattern to interrogate
> /proc/<pid>/environ to grab a crashing processes environment

This sounds like a potential way for us to implement a prototype core-file generator that includes the environ in the core proper?  We'll then still need to get it integrated into the kernel proper.

Comment 4 Neil Horman 2008-11-17 19:37:48 UTC
Not sure whats left to be done here.  The requestors account has been closed, and I think that the functionality that is required is implemented in 5.3 via the core_patter facility.  Does anyone with an interest in this bug have any more input here, or shall we close this as NEXTRELEASE?

Comment 5 Neil Horman 2009-04-17 11:02:51 UTC
closing, no response


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