On 04/01/2015 02:47 PM, Jeff Darcy wrote:
When doing an initial burn in test (regression run on master head
of GlusterFS git), it coredumped on the new "slave23.cloud.gluster.org" VM.
(yeah, I'm reusing VM names)
http://build.gluster.org/job/regression-test-burn-in/16/console
Does anyone have time to check the coredump, and see if this is
the bug we already know about?
This is *not* the same as others I've seen. There are no threads in the
usual connection-cleanup/list_del code. Rather, it looks like some are
in generic malloc code, possibly indicating some sort of arena corruption.
This looks like the other core I saw yesterday, which was not the usual
connection cleanup stuff. Adding this info here, as this brings this
core count upto 2.
One here, and the other in core.16937 : http://ded.ninja/gluster/blk0/
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
