I have the output from a Solaris
pstack on a core file. I don't understand how to map the numbers in the log to the parameters that were being used by the functions in question at the time of the segfault.
There seems to be more numbers in the output than the count of parameters to the function calls. Which numbers are the parameter values/addresses?
The manual is not at all helpful.
... fffffffec993a8a8 sigacthandler (b, ffffffff7fffd5e0, ffffffff7fffd300, 14b7b0, fffffffec9a86000, b) + 5c --- called from signal handler with signal 11 (SIGSEGV) --- fffffffeba4422b0 XmMessageBoxGetChild (100400, 5, 5, 0, 118, fffffffeba62e000) + e4 000000010026a83c GetMessageDialog (101317440, 0, ffffffff7fffe130, 100420, 100400, 127a94) + 214 000000010026ab0c _XmtDisplayMessage (101317440, 0, 1000c9510, 1011927e5, ffffffff7fffe240, 101192780) + 278 000000010026b048 XmtDisplayInformationMsg (1000c9000, 1000c9, 100000, 2, 0, ffffffff7fffe2f8) + 44 00000001001573ec _smog_w_alarm_post_ack_actions (101314990, 101192760, 1003a0, 1009f4970, 101317440, 100000) + 100 000000010015819c __select_cb (101314990, ffffffff7fffe560, 101317440, 10113bfc0, 1000916d0, 10120c9d0) + 1b4 0000000100257a04 XmtCallCallback (101314990, 100257, ffffffff7fffe560, 101183530, 0, 0) + 3c4 ...
The only two of our application functions involved are
_smog_w_alarm_post_ack_actions(), the others are Motif GUI/Widget Library calls. But, looking at our function definitions:
static void __select_cb( Widget w, XtPointer call_data ); void _smog_w_alarm_post_ack_actions( Widget w, Alarm_Public_Data *alarm );
There's only two arguments to each function. I expect one of the
Widget pointers is incorrect (probably pointing to a window that's already closed). I'd like to know which (if any) of those numbers maps to the actual parameter value/address to help in debugging the issue.