Update lib.rs

[20urc3]

I added the new error variants to the Error enum:

• Configuration - For errors related to incorrect configuration settings
• Compilation - For errors related to code compilation issues
• System - For system call failures and resource allocation problems
• Version - For version compatibility issues

And added their corresponding constructor methods for each new error type, following the same pattern as the existing constructors in the library.

[domenukk]

This is almost always identical to OsError, right? Maybe make OsError's io::Error be optional, instead

[domenukk]

Does this ever happen?

[20urc3]

Well yes

• System(String, ErrorBacktrace) → Err(Error::system("The fuzzing target reports that the shm_open() call failed.")) and similar system error messages
• Version(String, ErrorBacktrace) → Err(Error::version("The -c cmplog target was instrumented with an too old AFL++ version, you need to recompile it.")) and the other version error message

[domenukk]

I'd say it's fine to do
System(String, ErrorBacktrace) → Err(Error::os_error(None, "The fuzzing target reports that the shm_open() call failed.")) or os_error_str
(Error::illegal_state("The -c cmplog target was instrumented with an too old AFL++ version, you need to recompile it.")

[20urc3]

lgtm will do that

[domenukk]

is this different toIllegalArgument?

[domenukk]

Do you have use cases for each of those?

[20urc3]

Do you have use cases for each of those?

Those were deduced from fn report_error_and_exit(status: i32)

FS_ERROR_MAP_SIZE - Configuration issue
FS_ERROR_MAP_ADDR - Compilation issue
FS_ERROR_SHM_OPEN, FS_ERROR_SHMAT, FS_ERROR_MMAP - System-level issues
FS_ERROR_OLD_CMPLOG, FS_ERROR_OLD_CMPLOG_QEMU - Version compatibility issues

• Configuration(String, ErrorBacktrace) → Err(Error::configuration("AFL_MAP_SIZE is not set and fuzzing target reports that the required size is very large. Solution: Run the fuzzing target stand-alone..."))
• Compilation(String, ErrorBacktrace) → Err(Error::compilation("The fuzzing target reports that hardcoded map address might be the reason the mmap of the shared memory failed. Solution: recompile the target..."))
• System(String, ErrorBacktrace) → Err(Error::system("The fuzzing target reports that the shm_open() call failed.")) and similar system error messages
• Version(String, ErrorBacktrace) → Err(Error::version("The -c cmplog target was instrumented with an too old AFL++ version, you need to recompile it.")) and the other version error message

[domenukk]

Yeah.. I would prefer to map these on existing error codes, see my comment above

[20urc3]

Yeah.. I would prefer to map these on existing error codes, see my comment above

Ok for OSError instead of CompilationError, and where is defined toIllegalArgument?
For the System/Version i dont see existing error that correspond.

[domenukk]

Status?