Sorry it's been so long since my original email. Life happens sometimes. At any rate, I'm able to continue with debugging now.

First off, thanks to Timo and Lukas for their help! I was able to generate the backtrace and core dump file as Jakub suggested. Since it may contain sensitive data, I will email him the files directly.

Jakub, look for an email from my momentarily. Thanks for taking the time to help me out!


-Chris


On Mon, Jul 14, 2014 at 4:07 PM, Timo Aaltonen <tjaalton@ubuntu.com> wrote:
11.07.2014 11:42, Jakub Hrozek kirjoitti:
> On Thu, Jul 10, 2014 at 11:52:18PM +0200, Lukas Slebodnik wrote:
>> On (10/07/14 14:30), Chris Hartman wrote:
>>> Hi Jakub,
>>>
>>> Is it possible to generate a core file? That would help debugging quite a
>>>> lot.
>>>
>>> Thanks for your response. I'd be happy to generate a core file for you but
>>> I'm afraid I'm going to need some guidance.
>>>
>>> My google-fu has gotten me a little familiar with what commands are
>>> involved, but I'm not exactly sure how I'd go about generating or
>>> retrieving a core dump, especially because the sssd_be process is the one
>>> that's crashing, not the main sssd process.
>>>
>>> Would you be able provide assistance?
>> At first, you will need to install package with debug symbols.
>> Unfortunately, I was not able to find debug symbols for sssd in ubuntu 14.04.
>
> Maybe Timo (CC) has some tips here?

Ubuntu provides ddebs created on package build that you can install, see:

https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages


it'll get in Debian too eventually:

https://wiki.debian.org/AutomaticDebugPackages


--
t
_______________________________________________
sssd-users mailing list
sssd-users@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sssd-users