gluster-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gluster-devel] GlusterFS /home and KDE


From: NovA
Subject: Re: [Gluster-devel] GlusterFS /home and KDE
Date: Tue, 8 May 2007 13:23:17 +0400

Avati,
here it is backtrace you asked:
----
Core was generated by `[glusterfsd]
                             '.
Program terminated with signal 11, Segmentation fault.
#0  posix_locks_flush (frame=<value optimized out>, this=0x609060,
ctx=0x6102f0) at posix-locks.c:677
677         if (l->client_pid == pid) {
(gdb) bt
#0  posix_locks_flush (frame=<value optimized out>, this=0x609060,
ctx=0x6102f0) at posix-locks.c:677
#1  0x00002aaaaaebf4fb in fop_flush (frame=<value optimized out>,
bound_xl=0x609060, params=<value optimized out>) at proto-srv.c:646
#2  0x00002aaaaaeba694 in proto_srv_notify (this=<value optimized
out>, trans=0x604360, event=1) at proto-srv.c:2753
#3  0x00002b25736fc7e4 in sys_epoll_iteration (ctx=0x7fff375d6110) at epoll.c:53
#4  0x000000000040164c in main (argc=5, argv=0x7fff375d62a8) at glusterfsd.c:288
----
Hope this is what you want. I just did not knew how to use coredumps
(not needed in my work yet) :)...

WBR,
Andrey

2007/5/8, Anand Avati <address@hidden>:
Andrey,
 the core dump file as such is of no use since it has to be used along
with the binary which created it. what i want is a backtrace .. "gdb
glusterfsd -c core.pid" and type "bt" and send me the output, please
:)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]