Dear All, As we know, generally, we run bt command in gdb, gdb show the seg fault location in last backtrace. I found one strange behaviour If i run bt command in gdb, at that itme, gdb didn’t show the segment fault location in backtrace by default. Can some one tell the reason and is this expected in SMP warning: Unable to find dynamic linker. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. Core was generated by `./myapp'. Program terminated with signal 11, Segmentation fault. #0 malloc_consolidate (av=0x47600010) at malloc.c:5201 //not fault point thread running on CPU1 5201 malloc.c: No such file or directory. in malloc.c (gdb) bt #0 malloc_consolidate (av=0x47600010) at malloc.c:5201 #1 0x426eb1a8 in _int_malloc (av=0x47600010, bytes=<value optimized out>) at malloc.c:4435 gdb) info reg r0 0xfffe8ed4 4294872788 r1 0x427a8000 1115324416 r2 0x91 145 r3 0x708812d8 1887965912 r4 0x47600040 1197473856 r5 0x708812d8 1887965912 r6 0xb7e81318 3085439768 r7 0x47600040 1197473856 r8 0x476ec930 1198442800 r9 0x47600010 1197473808 r10 0x28 40 r11 0x70881130 1887965488 r12 0x47600018 1197473816 sp 0x431aeb20 0x431aeb20 lr 0x426eb1a8 1114550696 pc 0x426e819c 0x426e819c <malloc_consolidate+316> // also , program count show the CPU1 info fps 0x0 0 cpsr 0x60000010 1610612752 (gdb) info thread 225 Thread 190 0x00000000 in ?? () // real user fault point 224 Thread 132 __pthread_cond_wait (cond=0x41ddf060, mutex=0x41ddf090) Quit (gdb) thread 225 [Switching to thread 225 (Thread 190)]#0 0x00000000 in ?? () (gdb) bt #0 0x00000000 in ?? () (gdb) info reg r0 0x6de22ba0 1843538848 r1 0x476e1648 1198397000 r2 0x0 0 r3 0x0 0 r4 0x83407ef0 2202042096 r5 0x476e1648 1198397000 r6 0x68b3888 109787272 r7 0x0 0 r8 0x6de22ba0 1843538848 r9 0x6de22bf0 1843538928 r10 0x83407f44 2202042180 r11 0x6de22bd4 1843538900 r12 0x23f 575 sp 0x6de22b88 0x6de22b88 lr 0x1808774 25200500 pc 0x0 0 // program show the user fault info correctly of CPU0 fps 0x0 0 cpsr 0x20000010 536870928 Thanks, John