Bug#82600: zalloc panic

[Roland McGrath]

That location is inside the allocator, so just from the PC we don't know
what kind of thing is being allocated.  We need to see backtrace from the
panic.  If ddb works these days, you can use that and then put the PC
values through addr2line.  

I just checked in a simple change to zalloc.c to make all those panic
messages include zone->zone_name, which will tell us what the kernel
object involved is.  

You can also write a program using the <mach_debug/mach_debug.defs>
host_zone_info RPC to collect statistics on the zones and look for
balloons.  But in your case it looks like it's so quick you wouldn't have
the chance.  You might want to change the panics to print out zone
statistics when they panic.