kandi X-RAY | unfork Summary
kandi X-RAY | unfork Summary
unfork is a C++ library. unfork has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.
unfork(2) is the inverse of fork(2). sort of.
unfork(2) is the inverse of fork(2). sort of.
Support
Quality
Security
License
Reuse
Support
unfork has a medium active ecosystem.
It has 1416 star(s) with 37 fork(s). There are 23 watchers for this library.
It had no major release in the last 6 months.
unfork has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of unfork is current.
Quality
unfork has no bugs reported.
Security
unfork has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
unfork is licensed under the 0BSD License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
unfork releases are not available. You will need to build from source code and install.
Installation instructions are available. Examples and code snippets are not available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of unfork
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of unfork
unfork Key Features
No Key Features are available at this moment for unfork.
unfork Examples and Code Snippets
No Code Snippets are available at this moment for unfork.
Community Discussions
No Community Discussions are available at this moment for unfork.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install unfork
Keep in mind that this repository is nothing more than a proof of concept. You’ll need [patched](musl-no-vdso.patch) musl-gcc. (Using stock musl mostly works by accident on x86_64, but will usually crash on i386 without the patch.) After that, check the paths in the *.specs files, run make and it’s done. The demo code uses puts as an entry point and prints two messages; the first one using a clean snapshot of another process, and the second one reusing the same snapshot. Any process that dynamically loads libc.so works, e.g. /bin/cat. Run ./unfork[32|64].elf $(pidof cat) and enjoy. Although puts may seem trivial, it involves a surprisingly deep call stack (well… in glibc), syscalls, TLS, vDSOs, and is probably more complicated than the kind of problems I originally set out to solve.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page