Lines Matching defs:zalloc
59 * File: kern/zalloc.c
86 #include <kern/zalloc.h>
330 * Generally, you'll know you have a leak when you get a "zalloc retry failed 3" panic from the zone
362 * MAX_DEPTH configures how deep of a stack trace is taken on each zalloc in the zone of interrest. 15
374 * record is added to the log each time a zalloc() is done in the zone_of_interest. For leak debugging,
380 void *z_element; /* the element that was zalloc'ed of zfree'ed */
381 uint32_t z_opcode:1, /* whether it was a zalloc or zfree */
445 * Test if we want to log this zalloc/zfree event. We log if this is the zone we're interested in and
473 z = (zone_t) zalloc(zone_zone);
861 * zalloc returns an element from the specified zone.
925 panic("zalloc: zone \"%s\" empty.", zone->zone_name);
962 printf("zalloc did gc\n");
966 panic("zalloc: \"%s\" (%d elements) retry fail %d", zone->zone_name, zone->count, retval);
1019 panic("zalloc: \"%s\" (%d elements) zget_space returned %d", zone->zone_name, zone->count, retval);
1122 zalloc(
1230 * whether we're trying to catch a leak or corruption. See comments above in zalloc for details.
1363 * were never zalloc'd/zget'd. The correct way to stuff memory