Bug 762686 (GLUSTER-954) - quick-read crashes during init() on Mac OS X
Summary: quick-read crashes during init() on Mac OS X
Keywords:
Status: CLOSED DUPLICATE of bug 762455
Alias: GLUSTER-954
Product: GlusterFS
Classification: Community
Component: quick-read
Version: mainline
Hardware: All
OS: Mac OS
high
medium
Target Milestone: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-26 23:53 UTC by Vikas Gorur
Modified: 2015-12-01 16:45 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description Vikas Gorur 2010-05-26 23:53:43 UTC
#0  0x00007fff85d8284d in usleep$NOCANCEL ()
#1  0x00007fff85da1e3c in abort ()
#2  0x00007fff85d90ae5 in malloc_jumpstart ()
#3  0x00007fff85cb78b0 in malloc_zone_malloc ()
#4  0x00007fff85cb6b7c in malloc_zone_malloc ()
#5  0x00007fff85cb8cda in malloc_zone_calloc ()
#6  0x00007fff85cbc77b in calloc ()
#7  0x000000010004790b in __gf_calloc (nmemb=1, size=16, type=18) at ../../../libglusterfs/src/mem-pool.c:135
#8  0x00000001000ed9d1 in init (this=0x100814200) at ../../../../../xlators/performance/quick-read/src/quick-read.c:2578
#9  0x000000010002598e in xlator_init (xl=0x100814200) at ../../../libglusterfs/src/xlator.c:943
#10 0x000000010002553f in xlator_init_rec (xl=0x10080c818) at ../../../libglusterfs/src/xlator.c:836
#11 0x000000010002568c in xlator_tree_init (xl=0x10080c818) at ../../../libglusterfs/src/xlator.c:874
#12 0x00000001000026ba in _xlator_graph_init (xl=0x10080c818) at ../../../glusterfsd/src/glusterfsd.c:634
#13 0x00000001000028f8 in glusterfs_graph_init (graph=0x10080c818, fuse=0) at ../../../glusterfsd/src/glusterfsd.c:713
#14 0x0000000100004bfb in main (argc=7, argv=0x7fff5fbff9b0) at ../../../glusterfsd/src/glusterfsd.c:1476

Just starting GlusterFS will cause this crash.

Comment 1 Csaba Henk 2010-06-10 07:05:26 UTC

*** This bug has been marked as a duplicate of bug 723 ***


Note You need to log in before you can comment on or make changes to this bug.