linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: linux-os <linux-os@chaos.analogic.com>
To: Jan Frey <jan.frey@nokia.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] support for gzipped (ELF) core dumps
Date: Thu, 6 Jan 2005 08:30:25 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0501060826060.17938@chaos.analogic.com> (raw)
In-Reply-To: <1105017578.28175.1.camel@borcx178>

On Thu, 6 Jan 2005, Jan Frey wrote:

> Hi,
>
> I've written a patch for 2.4.28 kernel which enables writing of core
> dump files for ELF binaries in .gz format. This is interesting when
> using and debugging large binaries. In my case core files exceeded 1GB
> and got written via NFS...
> Anyhow, below patch is not really "beautiful", especially CRC looks
> quite annoying here. Consequently it is to be seen as "proof of concept"
> and I'm open for further discussion.
>
> Is anybody else interested in something like this at all?
>
> Regards,
> Jan

But that's what modules are for! It would nice to have a module
that could be inserted when the capability is needed. Certainly
you don't expect everybody to keep those unused CRC tables in
the kernel forever. Do you?

Cheers,
Dick Johnson
Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
  Notice : All mail here is now cached for review by Dictator Bush.
                  98.36% of all statistics are fiction.

  reply	other threads:[~2005-01-06 13:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 13:19 [PATCH] support for gzipped (ELF) core dumps Jan Frey
2005-01-06 13:30 ` linux-os [this message]
2005-01-06 13:43 ` Miquel van Smoorenburg
2005-01-08 17:27 Shaheed
2005-01-13 11:51 ` Jan Frey
2005-01-13 13:29   ` Shaheed

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=Pine.LNX.4.61.0501060826060.17938@chaos.analogic.com \
    --to=linux-os@chaos.analogic.com \
    --cc=jan.frey@nokia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /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;
as well as URLs for NNTP newsgroup(s).