Date: Tue, 2 Apr 2002 09:38:52 -0500 (EST) From: Robert Watson <rwatson@FreeBSD.org> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Marcel Moolenaar <marcel@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ia64/ia64 ia64dump.c Message-ID: <Pine.NEB.3.96L.1020402093647.20010Z-100000@fledge.watson.org> In-Reply-To: <xzp663ai5rw.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2 Apr 2002, Dag-Erling Smorgrav wrote: > Poul-Henning Kamp <phk@critter.freebsd.dk> writes: > > COOL! Thanks a LOT! > > *not* cool. We can't have every architecture team invent their own dump > format, or savecore(8) will be hell to maintain. Please don't introduce > any more breakage; I'll take care of this once I'm done with the mutex > profiling code. As long as no one expects the dump format to be static, we should have no problem as we migrate to desDUMP. What are the features missing from our older dump formats that are required -- the ability to sparsely store chunks of address space, etc? (Note: it would be very cool to be able to swap a hard disk from a sparc64 box to an i386 box, and have savecore dump the core from it to a system dump, then have cross-compiled gdb debug it. Of course, we have other problems before then -- are our disk labels endian-aware?) Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1020402093647.20010Z-100000>