"[ERR] Metavtab of <classname> lies outside all segments." should not be fatal

[Muirey03]

Currently the error [ERR] Metavtab of <classname> lies outside all segments. when using iometa -M is fatal and iometa terminates when it is encountered. It would be better if this error could be considered nonfatal and the class could be instead "skipped over" by iometa, allowing other classes to still be processed.

[Siguza]

I disagree.
There are a good bunch of issues that I made non-fatal, mostly when failing to find certain things at all. In those cases, I have no reason to believe that the things iometa does find are wrong. However, if any of the things found are clearly wrong (such as with the issue you're encountering), then I have strong reason to assume that other things are also wrong, and should not be trusted.

That said, would you mind telling me exactly what kernel you're getting this error on?

[Muirey03]

This was run on the 13.0 InternalUI leak's kernelcache. Changing the break to a continue allowed this class to be skipped and I was given a very detailed symbol map which I would be happy to include in this repository via a pull request.

[Siguza]

So, the commits of the past month included quite a bunch of bug fixes, and I ran the 1.5.0 build against every kernel I have available.
Could you try again and see if the issue persists on your kernel?

That said, I'd rather not include symbols from an internal kernel in this repo. The 12.0b1 and 14.0-Research kernels should give us virtually all the symbols we need, and associating with leaked/stolen material is not something I'm too keen on.