Bug#246288: Getting a very similar segfault here

2005-01-19 Thread Stef Epardaud
Hi. I could not run that program due to a segfault in the call to getgrouplist. After googling a little, I changed the 'compat' settings in /etc/nsswitch.conf to 'files nis' and all went well. Now dbus is up and running (and I gotta figure out how to make it do what I want, but that's anothing

Bug#246288: Getting a very similar segfault here

2005-01-16 Thread Stef Epardaud
Hi, I'm getting a segfault too, rendering dbus useless. Any time a client connects to it, it segfaults. I didn't manage to get a core dump even when starting it myself with 'ulimit -c unlimited'. However I've got some info. When I run the command DBUS_VERBOSE=1 dbus-daemon-1 --system --nofork I

Bug#246288: Getting a very similar segfault here

2005-01-16 Thread Stef Epardaud
On Sun, Jan 16, 2005 at 07:03:30PM +0100, Sjoerd Simons wrote: The socket opening stuff is something your nisbindings do, not a dbus thing. Could you trace the daemon with ltrace and provide the last part of the output. Ok, thanks for the quick reply, here goes: memmove(0x809bc9d, 0x809bc98,