How to analyze a core dump on a Profiler.

The profiler has created a core dump.

1. Find out what is causing the coredump and how many times.

   /usr/mazu/coredumps$ less backtrace-core.* | grep 'Core was generated' -c
482

   There are 482 lines in these files that say Core was generated by `/usr/mazu/bin/servicemanager'.

2. Look at backtrace file to find out what is causing the coredump.

   /usr/mazu/coredumps$ zcat backtrace-core.9692.txt.gz | less
[Thread debugging using libthread_db enabled]
Core was generated by `/usr/mazu/bin/servicemanager'.
Program terminated with signal 11, Segmentation fault.
0x081a07b1 in Services::Policy::find_policy_immed(DataKey const&) ()
0x081a07b1 in Services::Policy::find_policy_immed(DataKey const&) ()
0x081b4e02 in Services::PolicyTree::_load_service_bylocation(uint_id_t<&(Services::service_id_t_s)> const&, bool) ()
0x081b6348 in Services::PolicyTree::_load_service(uint_id_t<&(Services::service_id_t_s)> const&, bool) ()
0x081b6c20 in Services::PolicyTree::_update_policy_tree() ()
0x081b7018 in Services::PolicyTree::update_db(Services::ServiceSchemaID, long, uint_id_t<&(Services::service_id_t_s)> const&) ()
0x081978b5 in Services::ServiceManager::change_location_grp() ()
0x08199044 in Services::ServiceManager::ServiceManager(ControlThread*) ()
0x0818e147 in main ()

   This shows the servicemanager dumped core in PolicyTree/Policy::find_policy_immed function.

Cascade profiler