Segmentation Fault

During a 1 user Solaris test the CMS(Central Management Server) crashed. The core file was generated at 2AM, so you check the machine on which the database was running. You find an event logs that says "MS SQL Server: unknown error" and it was generated at around 2AM. You then extract the thread stacks from the core file, and you see that a thread had a segmentation fault (SIGSEGV). At the top of the stack you see that the thread was executing some Database Subsystem code of ours.

Question: What do you think is the most likely cause of the segmentation fault and why?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

My first thought is that

My first thought is that this is not appropriate for LtU...