Searched refs:dumpable (Results 1 – 18 of 18) sorted by relevance
286 extent_dumpable_set(extent_t *extent, bool dumpable) { in extent_dumpable_set() argument288 ((uint64_t)dumpable << EXTENT_BITS_DUMPABLE_SHIFT); in extent_dumpable_set()305 bool committed, bool dumpable) { in extent_init() argument317 extent_dumpable_set(extent, dumpable); in extent_init()
302 prctl-dumpable
303 prctl-dumpable \
275 prctl-dumpable.test \
356 prctl-arg2-intptr$(EXEEXT) prctl-dumpable$(EXEEXT) \1840 prctl_dumpable_SOURCES = prctl-dumpable.c1841 prctl_dumpable_OBJECTS = prctl-dumpable.$(OBJEXT)2818 prctl-dumpable.c prctl-name.c prctl-no-args.c \2965 prctl-dumpable.c prctl-name.c prctl-no-args.c \3765 prctl-dumpable \4217 prctl-dumpable.test \5879 prctl-dumpable$(EXEEXT): $(prctl_dumpable_OBJECTS) $(prctl_dumpable_DEPENDENCIES) $(EXTRA_prctl_dum…5880 @rm -f prctl-dumpable$(EXEEXT)7108 @AMDEP_TRUE@@am__include@ @am__quote@./$(DEPDIR)/prctl-dumpable.Po@am__quote@
753 If you want your pass to be easily dumpable, you should implement the virtual
752 If you want your pass to be easily dumpable, you should implement the virtual
80 - Refactor extent management with dumpable flag. (@davidtgoldblatt)
1755 Set the process "dumpable" flag when running in debug
8402 process dumpable flag is cleared, on ia64 this results to all syscall8408 This condition used to be triggered by prctl-dumpable test that caused8413 * tests/prctl-dumpable.c [__ia64__]: Skip the test.12348 process dumpable flag is cleared. As the first 4 syscall arguments are12352 This condition is triggered and therefore tested by prctl-dumpable test.13248 PTRACE_PEEKTEXT becames unavailable when the process dumpable flag is13252 This condition is triggered and therefore tested by prctl-dumpable test.18254 * tests/prctl-dumpable.test: Likewise.22263 * tests/prctl-dumpable.c: New file.22264 * tests/prctl-dumpable.test: New test.[all …]