null

Sort by

Searched refs:XPt (Results 1 - 7 of 7) sorted by relevance

/external/valgrind/main/massif/tests/
H A D	deep-B.stderr.exp	`51 Massif: XPt init expansions: ... 52 Massif: XPt later expansions: ...`
H A D	realloc.stderr.exp	`41 Massif: XPt init expansions: ... 42 Massif: XPt later expansions: ...`
H A D	deep-C.stderr.exp	`54 Massif: XPt init expansions: ... 55 Massif: XPt later expansions: ...`
H A D	peak2.stderr.exp	`109 Massif: XPt init expansions: ... 110 Massif: XPt later expansions: ...`
H A D	culling1.stderr.exp	`439 Massif: XPt init expansions: ... 440 Massif: XPt later expansions: ...`
H A D	culling2.stderr.exp	`542 Massif: XPt init expansions: ... 543 Massif: XPt later expansions: ...`
/external/valgrind/main/massif/
H A D	ms_main.c	79 // keeping XPt children sorted by 'ip' and use binary search in get_XCon. 84 // - In each XPt, record both bytes and the number of allocations, and 499 // An XPt represents an "execution point", ie. a code address. Each XPt is 508 // It's a bit of a fake XPt (ie. its 'ip' is zero), and is only used because 511 // Any child of 'alloc_xpt' is called a "top-XPt". The XPts at the bottom 514 // Each path from a top-XPt to a bottom-XPt through an XTree gives an 537 // XXX: make XPt and SXPt extensible arrays, to avoid having to do two 540 typedef struct _XPt XPt; typedef in typeref:struct:_XPt [all...]

Completed in 232 milliseconds