Date: Sat, 6 Jan 2007 14:29:37 -0800 From: Alfred Perlstein <alfred@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/usr.bin/kdump kdump.c Message-ID: <20070106222937.GV70403@elvis.mu.org> In-Reply-To: <200701051607.59334.jhb@freebsd.org> References: <200701052104.l05L4cO7037092@repoman.freebsd.org> <200701051607.59334.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* John Baldwin <jhb@freebsd.org> [070105 13:07] wrote: > > Sample before and after from a trivial case: > > old: > 9320 kdump USER 12 00 00 00 00 00 00 00 00 00 00 00 00 > 9320 kdump USER 12 00 00 00 00 01 04 00 00 00 08 21 08 > > new: > 9320 kdump USER malloc_init() > 9320 kdump USER 0x8210800 = malloc(1025) > > I also have patches I use at work that allow kdump to recognize a 32-bit > malloc utrace on an amd64 machine (for when you run an i386 binary) if folks > are interested. I'm not sure how many i386 on amd64 hacks we want in the > official CVS tree. :) I think a lot, a LOT of time people want to run intel on amd64, making that easier will make people happy. > I also have another set of patches to add various utrace(2) events to the > runtime linker as well as logic in kdump to parse them that I hope to commit > in the near future. Nice. -- - Alfred Perlstein, RED Incorporated Consulting. - coder / sysadmin / FreeBSD Hacker / All that jazz -
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070106222937.GV70403>