Self-Modifying Code

Concept

In the provided evidence, self-modifying code is discussed as an example of a reentrant instruction pattern that may execute more than once during a single generated test run. It appears in the context of Genesys-Pro stream-level test-program generation, where the stream solver can generate such reentrant behavior in a controlled way.

First seen 5/26/2026

Last seen 5/26/2026

Evidence 1 chunks

Wiki v1

WIKI

Overview

The provided source identifies self-modifying code as one example of a reentrant instruction pattern: an instruction or instruction sequence that can execute more than once during a single test run. Other examples listed in the same context include procedure calls, recurring interrupts, and user-defined loops.

Role in test-program generation

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

1 connections

Genesys-Pro ← mentions 85% 1e

Genesys-Pro mentions self-modifying code as a type of reentrant instruction

CITATIONS

3 sources

3 citations — click to collapse

[1] Self-modifying code is listed as an example of a reentrant instruction that can execute more than once in a single test run. [PDF] Genesys-pro: innovations in test program generation for functional ...

[2] Genesys-Pro separates generation into stream-level generation, which determines instruction order, and instruction-level generation, which creates specific instruction instances. [PDF] Genesys-pro: innovations in test program generation for functional ...

[3] The stream solver allows controlled generation of reentrant instructions and prohibits randomly generated loops to protect against infinite loops. [PDF] Genesys-pro: innovations in test program generation for functional ...