I had the same, or a similar problem. After looking at the strace output
more closely, I figured that the problem was too less stack space.
When I ran poplog as user root the SIGSEGV vanished and poplog started ok.
So I finally upped the limit on stackspace for users. It is defined in
the kernel include file /usr/include/linux/sched.h:
sched.h:#define _STK_LIM (1*1024*1024*1024) /* 1 GB for poplog */
the normal values was 8K, with 1G it works ok for me, and I never saw
any other problems.
Why poplog needs such a horrendous stack space limit for startup is
beyond me, but then if it works, who cares.
Hoping, this will help you,
Andreas
|