No, I'm thinking of some experiences from ages ago, where some compilers
would actually produce SIGSEGV errors due to incompatible stack and
procedure call standards between the compiler and some part of a lib used.
On 2014-02-06 13:38, James Carlson wrote:
On 02/06/14 07:33, Hans J. Albertsson wrote:
I'd have thought a SIGSEGV immediately on startup indicates a problem
with the compilers and/or library sets used???
Not necessarily. It's a bad pointer somewhere. It could be anywhere;
only an analysis of the core dump would reveal the problem.
I think you might be thinking of SIGKILL, which is used by ld.so.1 if
there's a runtime linkage error.
_______________________________________________
OpenIndiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
