On Mon, January 30, 2012 18:06, Stephen Gallagher wrote:
> On Mon, 2012-01-30 at 18:00 +0100, Sigbjorn Lie wrote:
>> Sure. Ive left the office for today, will do so tomorrow.
>> Im not very familiar with gdb. Any particular syntax / switches to
>> add?
>> Rgds,
>> Siggi.
> You'll want to do this in a non-graphical terminal, so you can switch to
> it if KDE gets into trouble.
> First, install the sssd-debuginfo packages (debuginfo-install sssd)
> and install gdb (yum install gdb)
> Then run:
> gdb -p ($pidof sssd_be)
> Then in the gdb prompt, type 'cont' (this will resume execution of
> sssd_be).
> Now, switch back to KDE and unlock the screen. Then switch back to this
> virtual terminal.
> You should be back at the prompt, with GDB telling you that you received
> Type "bt full" and reply with all pages of output from that (there may
> be multiple, requiring you to hit enter to see them).

Ok, please see below for the output from gdb.

I notice that it's not happening every time. All this morning I could unlock 
without any issues.
Around lunchtime the issue started occouring again, but it's different each 
time how many times I
have to restart sssd before I can successfully unlock my desktop.

warning: no loadable sections found in added symbol-file system-supplied DSO at
0x00002b104670cce3 in __epoll_wait_nocancel () from /lib64/libc.so.6
(gdb) cont

Detaching after fork from child process 22008.
Detaching after fork from child process 23608.
Detaching after fork from child process 28122.
Detaching after fork from child process 32315.

Program received signal SIGSEGV, Segmentation fault.
sysdb_attrs_get_el_int (attrs=0x6c616d726f6e2d72, name=0x43c75d "name",
    alloc=true, el=0x7fff3fafbb18) at src/db/sysdb.c:254
254         for (i = 0; i < attrs->num; i++) {

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) bt full
No stack.


Freeipa-users mailing list

Reply via email to