----- Original Message ----- > Krishnan Parthasarathi <kparthas@xxxxxxxxxx> wrote: > > > We need help in getting gdb to work with proper stack frames. It is mostly > > my lack of *BSD knowledge. > > What problem do you run into? On gdb'ing into one of the brick process, I see the following backtrace. This is seen with other threads in the process too. This makes it difficult to analyse what could have gone wrong. Is there something I am missing? Thread 1 (process 15311): #0 0xbb35d7d7 in _sys___nanosleep50 () from /usr/lib/libc.so.12 #1 0xbb688aa7 in __nanosleep50 () from /usr/lib/libpthread.so.1 #2 0xbb3cbcd7 in sleep () from /usr/lib/libc.so.12 #3 0xb9cef8da in posix_health_check_thread_proc (data=0xbb1db030) at posix-helpers.c:1685 #4 0xbb68cbca in ?? () from /usr/lib/libpthread.so.1 #5 0xbb3acbb0 in __mknod50 () from /usr/lib/libc.so.12 #6 0xb7aa5000 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
