Nick Renieris

I currently hardcode the resolution which is pretty bad.

KB (+KiB), MB (+MiB), etc https://www.wikiwand.com/en/Byte#/Multiple-byte_units Would presumably be added here: https://github.com/xoofx/kalk/blob/master/src/Kalk.Core/units.kalk#L48

Make triggered memory breakpoint address available in expressions

5

### Description It's not already available is it? I couldn't find anything in docs. My use case is that there's a large area of function pointers that I have put...

`NtBuildNumber` located in `KUSER_SHARED_DATA` for Windows 10, contains the build number. I don't see volatility using this anywhere. Instead it scans the memory to find KDBG for it, which seems...

Fix SceAvPlayer/libscemp4 LLE

6

Used by _many_ commercial games. Can use this hb for testing: http://vitadb.rinnegatamante.it/#/info/364

Add better filesystem abstraction layer

4

As I said in Discord: it's too 'anything goes' currently, in some places we use C++ api (fstream), in some others C api (fopen, etc), in some others native APIs......

Load (LLE) kernel modules

1

Load kernel modules (`elf`s embedded in `bootimage.skprx`) like we can do for user modules. Pretty easy with some `load_self` modifications, it hardly uses anything from the SELF header. With this...

https://wiki.henkaku.xyz/vita/SceLibKernel#Thread_specific_data Currently we don't init any data there, some of those fields would be quite easy to do, and it might help LLE'd modules.

C++20 keyword 'module' conflict in header

1

Yara is unusable in C++20 projects because `module` is now language keyword, and Yara declares it on an externally-visible header: https://github.com/VirusTotal/yara/blob/master/libyara/include/yara/modules.h#L213

Common word 'parent' defined in header

1

This: https://github.com/VirusTotal/yara/blob/master/libyara/include/yara/modules.h#L214 makes Yara unusable in any project that has functions/methods/etc named `parent` which seems quite common. It does break my own project since I have methods named that way....