This command used to take several minutes to run on ceph-mon or ceph-osd. Currently, on recent versions of Debian and Fedora it can take closer to an hour to run this command on ceph-osd on my laptop and over half an hour on a reasonably powerful server. I believe, but don't know, that this is an issue with objdump and not ceph and I am happy to pursue this further (and will) but I'm wondering if it is time to revisit the message we print with every crash dump? "NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this." This is not true in all cases such as where we know exactly which binary for which arch and OS was in use and, at least for now, it would be quicker and easier to just upload the binary anyway. It is also not true in the event we have a core file and can determine which binary was in use. Is it time to take another look at this and perhaps, as Kefu suggested, merely print the URL of a page which outlines steps and requirements for post-mortem debugging? -- Cheers, Brad -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
