On Tue, 24 Nov 2009 15:53:28 +0100 Jakub Witkowski <[email protected]> wrote:
> The backtrace follows: > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7fd9c68ac700 (LWP 22199)] > 0x000000000042713f in rxi_Start (event=0x0, arg0=0x1380e00, arg1=0x0, > istack=0) at rx.c:5287 5287 struct rx_peer *peer = > call->conn->peer; (gdb) backtrace > #0 0x000000000042713f in rxi_Start (event=0x0, arg0=0x1380e00, > arg1=0x0, istack=0) at rx.c:5287 #1 0x00007fd9c4bff4f0 in > rxi_ReadProc () from /lib/libnss_afs.so.2 #2 0x00007fd9c4bffa70 in Okay, yeah, you're in libnss-afs. Talk to Adam Megacz, or wherever libnss-afs bugreports should go. > For me, it's intriguing that this /only/ happens for aklog. I have > tested various other tools, including a short test program to directly > test of getuid and getpwuid, everything works like it should. I would guess there's some odd interactions between applications that use RX that make calls into libnss-afs, but I wouldn't know. -- Andrew Deason [email protected] _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
