Build error with current trunk branch

[f-yildirim]

Hi,
The following error occurs while building the current trunk branch.

FAILED: Userland/CMakeFiles/FileSystem.elf /home/fatih/development/rtos/pico-os/pico-os_github/build/Userland/CMakeFiles/FileSystem.elf
cd /home/fatih/development/rtos/pico-os/pico-os_github/build/Userland && /home/fatih/development/rtos/pico-os/pico-os_github/build/Tools/ElfEmbed
/usr/include/c++/15/optional:1172: constexpr _Tp* std::optional<_Tp>::operator->() [with _Tp = Elf::StringTable]: Assertion 'this->_M_is_engaged()' failed.
Aborted (core dumped)
ninja: build stopped: subcommand failed.

[muditbhargava66]

Hi @f-yildirim,

I encountered this build failure as well. The assertion Assertion 'this->_M_is_engaged()' failed in ElfEmbed usually indicates that the ELF string table wasn't correctly initialized or written, often due to issues with the underlying MemoryStream.cpp implementation.

I found that the tools were relying on Linux-specific system calls like memfd_create and copy_file_range, which can be unreliable or unavailable in certain environments (and completely unsupported on macOS).

I've just submitted a PR that resolves this by rewriting the MemoryStream.cpp implementation to use standard ANSI C file I/O (tmpfile, fread, fwrite), making the build robust across different Linux distros and macOS.

The fix is included in PR #9 which also adds:

• Deadlock detection for spinlocks
• Major documentation overhaul
• VSCode integration

Hope this helps!

[f-yildirim]

Hi @muditbhargava66 ,

I appreciate your support for pico-rtos and now for pico-os :)

I checkout your fix/build-errors-and-improvements branch.
But unfortunately the same issue is still there.

Thanks..

[muditbhargava66]

Hi @f-yildirim, Did you check the updated codebase and are there any issues in it?

[f-yildirim]

Hi @muditbhargava66 ,

I've just seen your last two commits, haven't checked them yet.
I will check and inform you.

Thanks..

[f-yildirim]

Hi @muditbhargava66 ,

I checkout your latest commits, unfortunately exactly the same issue exists.

Thanks..