1fb6a7d893
The old implementation tried to move forward as long as the current byte looks like a UTF-8 character continuation byte (has its two most significant bits set to 10). This is correct as long as we assume the string is actually valid UTF-8, which we do (we also have a separate method that can check whether it is the case). We can't, however, assume that the data after the end of our string is also valid UTF-8 (in fact, we're not even allowed to look at data outside out string, but it happens to a valid memory region most of the time). If the byte after the end of our string also has its most significant bits set to 10, we would move one byte forward, and then fail the m_length > 0 assertion. One way to fix this would be to add a length check inside the loop condition. The other one, implemented in this commit, is to reimplement the whole function in terms of decode_first_byte(), which gives us the length as encoded in the first byte. This also brings it more in line with the other functions around it that do UTF-8 decoding. |
||
|---|---|---|
| .github | ||
| AK | ||
| Applications | ||
| Base | ||
| Demos | ||
| DevTools | ||
| Documentation | ||
| Games | ||
| Kernel | ||
| Lagom | ||
| Libraries | ||
| Meta | ||
| Ports | ||
| Servers | ||
| Shell | ||
| Toolchain | ||
| Userland | ||
| .clang-format | ||
| .gitignore | ||
| .travis.yml | ||
| Contributing.md | ||
| LICENSE | ||
| Makefile.common | ||
| ReadMe.md | ||
Serenity
Graphical Unix-like operating system for x86 computers.
About
I always wondered what it would be like to write my own operating system, but I never took it seriously. Until now.
Serenity is a love letter to '90s user interfaces with a custom Unix-like core. It flatters with sincerity by stealing beautiful ideas from various other systems.
Roughly speaking, the goal is a marriage between the aesthetic of late-1990s productivity software and the power-user accessibility of late-2000s *nix. This is a system by me, for me, based on the things I like.
If you like some of the same things, you are welcome to join the project. It would be great to one day change the above to say "this is a system by us, for us, based on the things we like." :^)
I regularly post raw hacking sessions and demos on my YouTube channel.
Sometimes I write about the system on my github.io blog.
There's also a Patreon if you would like to show some support that way.
Screenshot
Current features
- Pre-emptive multitasking
- Multithreading
- Compositing window server
- IPv4 networking with ARP, TCP, UDP and ICMP
- ext2 filesystem
- Unix-like libc and userland
- POSIX signals
- Shell with pipes and I/O redirection
- mmap()
- /proc filesystem
- Local sockets
- Pseudoterminals (with /dev/pts filesystem)
- Filesystem notifications
- JSON framework
- Low-level utility library (LibCore)
- Mid-level 2D graphics library (LibDraw)
- High-level GUI library (LibGUI)
- HTTP downloads
- SoundBlaster 16 driver
- Software-mixing sound daemon
- WAV playback
- Simple desktop piano/synthesizer
- Visual GUI design tool
- PNG format support
- Text editor
- IRC client
- Simple painting application
- DNS lookup
- Desktop games: Minesweeper and Snake
- Ports system (needs more packages!)
- Other stuff I can't think of right now...
How do I build and run this?
Make sure you have all the dependencies installed:
sudo apt install libmpfr-dev libmpc-dev libgmp-dev e2fsprogs qemu-system-i386 qemu-utils
Ensure your gcc version is >= 8 with gcc --version. Otherwise, install it (on Ubuntu) with:
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get install gcc-8 g++-8
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 800 --slave /usr/bin/g++ g++ /usr/bin/g++-8
Go into the Toolchain/ directory and run the BuildIt.sh script. Then source the UseIt.sh script to put the i686-pc-serenity toolchain in your $PATH.
Once you've done both of those, go into the Kernel/ directory, then run
./makeall.sh, and if nothing breaks too much, take it for a spin by using
./run.
Later on, when you git pull to get the latest changes, there's no need to rebuild the toolchain. You can simply rerun ./makeall.sh in the Kernel/ directory and you'll be good to ./run again.
Notes on WSL
SerenityOS can also be build and run under WSL Version 2. WSL Version 1 is not supported since Version 1 does not support ext2, which is needed for the setup.
WSL Version 2 is currently only available for Insider Builds of Windows which are more unstable and prone to crashes. Therefore, running SerenityOS on WSL Version 2 and running Insider Builds, in general, is not recommended on production systems.
Nevertheless, here is a guide on how to get an Insider Build and how to get WSL2. The installation then procedes as usual.
WSL2 does not natively support graphical applications. This means that to actually ./run SerenityOS, you need an X Server for windows. Vcxsrv is a good option. When you start up Vcxsrv, make sure to set the Display number to 0, and to Disable access control. Before actually doing ./run, you need to set the DISPLAY environmental variable as such:
export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0
This is due to a bug in WSL2. For more information, microsoft/WSL#4106.
Now you can finally, ./run.
IRC
Come chat in #serenityos on the Freenode IRC network.
Author
- Andreas Kling - awesomekling
Contributors
- Robin Burchell - rburchell
Feel free to append yourself here if you've made some sweet contributions. :)
License
Serenity is licensed under a 2-clause BSD license.