code wiki / _hdl_build / nx_static_field_probe.nx

nx_static_field_probe.nx

buildroot/runtime/_hdl_build/nx_static_field_probe.nx

2520 B51 linesdepth 2pulls 2 transitivereach 0 importersview sourcekind probetopic static
docsdependenciesstructsconstsfunctions

about

nx_static_field_probe.nx -- is "read struct FIELD through a STATIC pointer" a general nx_cc trap (pre-existing) or something specific? Minimal: a struct, a static pointer to a heap instance, write fields, then read the SAME field through the static ptr vs a local copy. If they disagree, the trap is general + pre-existing (unrelated to the sext bless, which touched only subword-load signedness). expect_exit: 0 license_tier: ORIGINAL

dependencies 1 imports · 0 importers

nx_syscalls.nx nx_static_field_probe.nx

imports: nx_syscalls.nx

imported by: nobody (leaf or entry point)

call flow from main pre-order; caps 40 nodes / depth 6 declared; ↻ = already shown

main sys_mmap p sys_write pn sys_mmap ↻ sys_write ↻

structs

8struct SFP { a: i64, b: i64, c: i64, d: i64 }

consts

none

functions

12func p(s: *u8) -> i64 { var n: i64=0; while s[n]!=(0 as u8){n=n+1} sys_write(1,s,n); return 0 }
called by 1: main calls 1: sys_write
13func pn(v: i64) -> i64 { let b: *u8=sys_mmap(28); var m: i64=v; if m<0{sys_write(1,"-" as *u8,1);m=0-m} let t: *u8=sys_mmap(28); var k: i64=0; if m==0{t[0]=48 as u8;k=1} while m>0{t[k]=(48+(m%10)) as u8;m=m/10;k=k+1} var i: i64=0; while i<k{b[i]=t[k-1-i];i=i+1} sys_write(1,b,k); return 0 }
called by 1: main calls 2: sys_mmapsys_write
15func main() -> i64
calls 3: sys_mmapppn