On 13.02.2013 05:57, Andrew Beekhof wrote:: > This link has some useful info: > > https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages
For corosync, we build -dbg package, so one can just install corosync-dbg. Since this is a pacemaker related problem, one should add ddebs archive and install debugging package: echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-security main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | \ sudo tee -a /etc/apt/sources.list.d/ddebs.list sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01 sudo apt-get update sudo apt-get install pacemaker-dbgsym libpengine3-dbgsym \ libpe-rules2-dbgsym libpe-status3-dbgsym libcrmcluster1-dbgsym \ libcrmcommon2-dbgsym libtransitioner1-dbgsym it wouldn't hurt to add corosync too: sudo apt-get install corosync-dbgsym Once you install those, debugging symbols will be in /usr/lib/debug. Files in /var/crash are not (just) cores. Those are files generated by apport, they contain core (base64) and other useful information. These files may contain private information, but that's probably not the case with pacemaker's crash. _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
