If you wish to work in another directory, the usual
PATH issues apply for locating the pelf program. FLAIR pattern files are ASCII text files
containing patterns for each exported function within the library being parsed. Patterns
are generated from the first 32 bytes of a function, from some intermediate bytes of the
function for which a CRC16 value is computed, and from the 32 bytes following the
bytes used to compute the cyclic redundancy check (CRC). Pattern formats are described
in more detail in the pat.txt file included with FLAIR. The second step in creating a sig
file is to use the sigmake tool to create a binary signature file from a generated pattern
file. The following command attempts to generate a sig file from the previously generated
pattern file:
# ../sigmake.exe -n"FreeBSD 6.2 standard C library" \
> libc_FreeBSD62.pat libc_FreeBSD62.sig
See the documentation to learn how to resolve collisitions.
: modules/leaves: 13443664/988, COLLISIONS: 924
The ??“n option can be used to specify the ???Library name??? of the sig file as displayed in
the sig file selection dialog box (see Figure 13-1). The default name assigned by sigmake
is ???Unnamed Sample Library.??? The last two arguments for sigmake represent the input
pattern file and the output sig file respectively.
Pages:
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569