malloc函数会引起段错误吗？？？？？

bin_linux96

大家帮忙看下，这是用mipsel-linux-uclibc-gdb调试打印出的堆栈信息
为什么死在了malloc这里，我的程序是多线程的..................

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 5053]
0x2b44ff34 in __malloc_consolidate () from /work/lib/libc.so.0
(gdb) bt
#0  0x2b44ff34 in __malloc_consolidate () from /work/lib/libc.so.0
#1  0x2b44f07c in malloc () from /work/lib/libc.so.0
#2  0x2b42892c in _stdio_fopen () from /work/lib/libc.so.0
#3  0x4db7cfac in gm_ddxdaemon_entry () from /work/lib/libgm_daemon.so
#4  0x2b3b0a4c in ddxdaemon_entry () from .//libddxdaemon.so//ddxdaemon_entyr是我启动的线程
#5  0x2b37f620 in start_thread () from /work/lib/libpthread.so.0
#6  0x2b3891e0 in __thread_start () from /work/lib/libpthread.so.0
Backtrace stopped: frame did not save the PC

suanmeilizhi

求代码

bin_linux96

回复 2# suanmeilizhi


    是公司项目代码，可以能比较复杂，所以不好贴出来..........

xingjiu119

一般malloc产生段错误都是前面的内存错误引起的，比如越界啥的。可以把malloc函数前移，然后适当添加些打印，什么时候不段错误了应该就能定位到大体位置了。