public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Christopher S. Aker" <caker@theshore.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [Feature Request?] Inline compression of process core dumps
Date: 12 Apr 2007 19:45:52 +0200	[thread overview]
Message-ID: <p73ps697agf.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070412164251.GC11736@ti88.telemetry-investments.com>

"Bill Rugolsky Jr." <brugolsky@telemetry-investments.com> writes:
> 
> The current functionality doesn't parse command line arguments into argv,
> nor provide the % variable replacements in the environment, so it is
> somewhat less useful than it could be. 

That was intentional because all this information is in the core dump itself
or in the environment.

-Andi

  reply	other threads:[~2007-04-12 16:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12 15:52 [Feature Request?] Inline compression of process core dumps Christopher S. Aker
2007-04-12 16:09 ` Bill Rugolsky Jr.
2007-04-12 16:18 ` Guillaume Chazarain
2007-04-12 16:28 ` Alan Cox
2007-04-12 16:42   ` Bill Rugolsky Jr.
2007-04-12 17:45     ` Andi Kleen [this message]
2007-04-13  2:22       ` Christopher S. Aker
2007-04-13  2:38         ` Randy Dunlap
2007-04-13  2:57           ` Christopher S. Aker
2007-04-13  4:21             ` Jeff Dike
2007-04-13 10:55             ` Alan Cox
2007-04-13 12:23               ` Andi Kleen
2007-04-13 14:59                 ` Randy Dunlap
2007-04-13 15:43                   ` Andi Kleen
2007-04-13 16:17                   ` Alan Cox
2007-04-13 19:42                     ` Andi Kleen
2007-04-13 12:39         ` Alan Cox
2007-04-13 13:38           ` Christopher S. Aker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=p73ps697agf.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=brugolsky@telemetry-investments.com \
    --cc=caker@theshore.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox