cdsfsbasu@cdsfmsb3 rust-cfb % target/debug/examples/cfbtool ls TetherLib.SchLib thread 'main' panicked at 'calledResult::unwrap()on anErrvalue: Custom { kind: InvalidData, error: "Malformed directory entry (non-zero storage start sector: fffffffe vs ffffffff)" }', examples/cfbtool.rs:121:50 note: run withRUST_BACKTRACE=1environment variable to display a backtrace
I'm sure they are not compliant, but it is useful to be able to read them. If the correctness is an issue, maybe you can put a feature in place ("loose-mode") or something that ignores these types of non-compliances?
…from Altium Designer.
Altium designer creates CFBs with the following:
cdsfsbasu@cdsfmsb3 rust-cfb % target/debug/examples/cfbtool ls TetherLib.SchLib thread 'main' panicked at 'called
Result::unwrap()on an
Errvalue: Custom { kind: InvalidData, error: "Malformed directory entry (non-zero storage start sector: fffffffe vs ffffffff)" }', examples/cfbtool.rs:121:50 note: run with
RUST_BACKTRACE=1environment variable to display a backtrace
I'm sure they are not compliant, but it is useful to be able to read them. If the correctness is an issue, maybe you can put a feature in place ("loose-mode") or something that ignores these types of non-compliances?