Fun trivia about my embedded systems work

- dereferencing 0 is fine
- dereferencing 0x1000 causes a kernel exception


I need to access this memory space, VXWORKS! That's 8MiB (less 4k) that you're not letting me have!

You know what fucks me up most about this?

I can use memmove(0xfff, source, len); to write beyond the 4k boundary, and memmove will SUCCEED! When memmove returns, my task will be murdered, but AFTER it writes into """forbidden memory"""

Sign in to participate in the conversation

cybrespace: the social hub of the information superhighway

jack in to the mastodon fediverse today and surf the dataflow through our cybrepunk, slightly glitchy web portal