nm core dumpping

[Checkpoint Technologies]

   I'm posting this for a friend who is having some trouble building a
shared library.  I confess I don't understand the procedures for this,
but will try to relate his predicament as best I can.

   He's building a shared library, which requires preparing a file
describing relocation and global symbol resolution.  When he has more
than 199 symbols to be resolved, the 'mkshlib' command finishes but
the resulting .a file does not have all the needed symbols.  After
exploring he discovered that one step in mkshlib was spawning nm, and
nm would core-dump.  (Peripheral to this is that mkshlib did not
report any error.)

    We're using Interactive Unix 2.2.  This appears to be common to
System V/386 3.2 Unix, because we borrowed a copy of nm from an SCO Unix
system, and it behaved identically.

    We are currently working around this by carefully tuning this
library to require less than 200 symbols, but I doubt this technique
will last (the library in question is under development right now, and
is expanding). If anyone has any help to offer, I'd be grateful.
-- 
First comes the logo: C H E C K P O I N T  T E C H N O L O G I E S      / /  
                                                                    \\ / /    
Then, the disclaimer:  All expressed opinions are, indeed, opinions. \  / o
Now for the witty part:    I'm pink, therefore, I'm spam!             \/