Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Snyder <msnyder@cygnus.com>,
	gdb-patches@sources.redhat.com, cagney@redhat.com,
	kettenis@science.uva.nl, kevinb@redhat.com,
	orjan.friberg@axis.com
Subject: Re: [RFA] New "generate-core-file" command, supercedes previous
Date: Fri, 04 Jan 2002 12:22:00 -0000	[thread overview]
Message-ID: <3C360DBC.D3720457@redhat.com> (raw)
In-Reply-To: <20020104140453.A26863@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> On Thu, Jan 03, 2002 at 05:51:51PM -0800, Michael Snyder wrote:
> > OK, this submission supercedes the previous one for the gcore command.
> > The command is now called "generate-core-files", with gcore as an alias.
> >
> > This patch can now generate multi-threaded corefiles both on solaris
> > and on linux.  The host makefile fragments for sparc-solaris and for
> > i386-linux have been updated to bring in the new code.  The new code
> > will not affect any other targets until their makefile fragmemts are
> > modified to pull it in.  It should work as-is for any flavor of
> > Solaris or Linux, but I've only tested sparc and i386 respectively.
> >
> > As before, there is a patch for bfd appended, which has not yet
> > been approved by the bfd/binutils maintainers.
> >
> > I'm now ready to formally request approval -- though there's still
> > room for improvement, I believe it's mature enough to check in.
> 
> It looks solid to me.  I especially like the supporting multiple
> threads bit.
> 
> For future consideration, it would be -very- nice if this supported
> writing sparse files.  That will, of course, require a BFD change.
> Right now, the dump for a 12-threaded application is about 25MB virtual
> size and no more than 1MB physical on-disk size, because the stacks for
> each thread are a 2MB sparse region.

Yes, Andrew and I have discussed that a bit.  Definitely desireable, 
maybe possible, probably requires bfd extension.  At some point we
should kick it around some more.


      reply	other threads:[~2002-01-04 20:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-03 17:57 Michael Snyder
2002-01-04 11:04 ` Daniel Jacobowitz
2002-01-04 12:22   ` Michael Snyder [this message]

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=3C360DBC.D3720457@redhat.com \
    --to=msnyder@redhat.com \
    --cc=cagney@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@science.uva.nl \
    --cc=kevinb@redhat.com \
    --cc=msnyder@cygnus.com \
    --cc=orjan.friberg@axis.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