Finally I found a workaround for this bug after postring to eclipse's bugzilla.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=233951
You have to set the environment variable MALLOC_CHECK_ to 0 then start eclipse.
This issue has been fixed in Eclipse 3.4 which is about to be released soon.