I'm still guessing, but perhaps cd /tmp ulimit -c `which gmond` --debug_level=1 -i eth0 gdb `which gmond` core
to get to some directory to which the user 'nobody' can write; perhaps gmond is not able to dump a core file in ~root after having setuid'd to nobody. -neil On Sun, Apr 07, 2002 at 01:13:11PM -0400, Mike Snitzer wrote: > I can't get gmond to drop a core file when it seg faults... I used ulimit > to set core to unlimited: > > [EMAIL PROTECTED] ~]# ulimit -a > core file size (blocks) unlimited > data seg size (kbytes) unlimited > file size (blocks) unlimited > max locked memory (kbytes) unlimited > max memory size (kbytes) unlimited > open files 1024 > pipe size (512 bytes) 8 > stack size (kbytes) 8192 > cpu time (seconds) unlimited > max user processes 16383 > virtual memory (kbytes) unlimited > > Any ideas? > > Mike > > Neil Spring ([EMAIL PROTECTED]) said: > > > On Sat, Apr 06, 2002 at 05:40:59PM -0500, Mike Snitzer wrote: > > > Any recommendations for accurately debugging gmond would be great; cause > > > when running through strace and gdb I can't get it to segfault. > > > > you might have already tried this, but > > > > unlimit core (or ulimit -c for bash) > > `which gmond` --debug_level=1 -i eth0 > > gdb `which gmond` core > > > > or is gdb unable to sort out the threads? > > > > -neil > > > > _______________________________________________ > Ganglia-general mailing list > Ganglia-general@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ganglia-general
