These are exposed by a shorten-64-to-32 warning from clang that is turned
out automatically when building release build for OSX.

They can be also triggered manually with similar configuration like this:

    CC=clang CFLAGS=-Wshorten-64-to-32 ./configure && make -j8

Should fix #2967

Without the config, clang complains about conflicting types

reader-tr03119.c:138:5: error: conflicting types for 'escape_pace_input_to_buf'
int escape_pace_input_to_buf(sc_context_t *ctx,
    ^
./reader-tr03119.h:87:5: note: previous declaration is here
int escape_pace_input_to_buf(sc_context_t *ctx,
    ^

The po->C_GetInterface is passed the callers ppInterface where
*ppInterface may not be valid.

if the po->C_GetInterface may not update the *ppInterface and return
an error. In this case  spy_interface_function_list should not be called,
as it assumes the *ppInterface has been modified.

Found debugging FireFox version 121 where FireFox passes a ppInterface
where *ppInterface is not a valid pointer, causing a segfault in
spy_interface_function_list.

FireFox calls C_GetInterface twice with flags = CKF_INTERFACE_FORK_SAFE
twice then on third time requests with flag = 0  where po->GetInterface
can support and it updates the *ppInterface  with valid data.

See #2987

 On branch pkcs11-spy-segfault
 Changes to be committed:
	modified:   pkcs11-spy.c

This allows for voluntary formatting with clang-format (or
IDE tools like clang-format plugin for VS Code).

Once a suitable formatting configuration is found, automatic formatting
can be configured

Tweaked by Jakub Jelen

Usage:

git config blame.ignoreRevsFile .ignoreRevsFile

Thanks OSS-Fuzz
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65834

Thanks OSS-Fuzz
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=65882

…anual pages