db_vid_get_map_id_V000

Part of Firmware Reversing.

• String location: file offset 0x9f87a4 (plain debug-string scan, not the symbol table)
• Status: ⚪ Name only — no code address found
• Also known as: fp_db_vid_get_map_id (a related debug string)

"vid" = virtual id, i.e. this project's own vnodeID naming. Given a virtual node id, this accessor is named for the step that resolves which MAP contains it — one half of the "which tile do I even need to open" step this project has wanted since eeu.il's own vnodeID field was first found (README §3.2).

Why there's no address

Confirmed structurally, not just by absence: a direct lis/addi absolute-address cross-reference scan (39,715 candidate pairs) and a whole-file literal-pointer scan both found zero matches for this specific string's own location. Most likely explanation: this is a DWARF-.debug_str-style debug-only string, structurally never referenced by executing code — the same conclusion independently reached for the 77-name db_*_V0NN accessor catalog this belongs to. See Firmware Reversing and research/swl_5238_reader.py's own docstring for the full negative- result writeup.

Real code that plausibly implements this concept may exist somewhere in the reachable <9MB range under a completely different (real, compiler-assigned) name — the symbol table has not been exhaustively searched for a semantic match, only for exact name matches, which found none.