tools/perf/tests/demangle-java-test.c

File Facts

System

Linux kernel

Corpus path

tools/perf/tests/demangle-java-test.c

Extension

.c

Size

1550 bytes

Lines

50

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• string.h
• stdlib.h
• stdio.h
• linux/kernel.h
• debug.h
• symbol.h
• tests.h

Detected Declarations

• function test__demangle_java

Annotated Snippet

if (!buf) {
			pr_debug("FAILED to demangle: \"%s\"\n \"%s\"\n", test_cases[i].mangled,
				 test_cases[i].demangled);
			continue;
		}
		if (strcmp(buf, test_cases[i].demangled)) {
			pr_debug("FAILED: %s: %s != %s\n", test_cases[i].mangled,
				 buf, test_cases[i].demangled);
			ret = TEST_FAIL;
		}
		free(buf);
	}

	return ret;
}

DEFINE_SUITE("Demangle Java", demangle_java);

Annotation

• Immediate include surface: `string.h`, `stdlib.h`, `stdio.h`, `linux/kernel.h`, `debug.h`, `symbol.h`, `tests.h`.
• Detected declarations: `function test__demangle_java`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.