Issue 58113 (opensc): Unusable traces pointing to linked library

Lately, we received issue 58113 (https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58113) with quite unusable traces

```
Direct leak of 40 byte(s) in 1 object(s) allocated from:
#0 0x5318e6 in malloc /src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:69:3
#1 0x795693544c0d in CRYPTO_zalloc
```

pointing to some function from a linked library (OpenSSL). However, the issue was hidden in the actual tested project, not the linked library. Is there something that can be done about it, or is it a problem regarding the underlying `libFuzzer` engine?

Start with OSS-Fuzz issue 10375 and the linked OSS-Fuzz report 58113, then inspect the sample trace showing allocation in OpenSSL's CRYPTO_zalloc. Determine whether the unusable trace comes from OSS-Fuzz configuration or the underlying libFuzzer engine; done means documenting the cause and a concrete way to produce traces that identify the tested project.

Written by the indexing model from the issue text.