adb logcat how to output the call stack

When I run a program error,
I use adb logcat get the following error message.

 F / libc (3871): Fatal signal 11 (SIGSEGV) at 0x00000000 (code = 1) 
I / DEBUG (115): ******************************************* ***** 
I / DEBUG (115): Build fingerprint: 'intel/mfld_dv10/mfld_dv10: 4.0.4/IMM76D/release.20130301: eng / dev-keys' 
I / DEBUG (115): pid: 3871, tid: 3871 >>> com.example.apis <<<< br />I / DEBUG (115): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000 
I / DEBUG (115): eax 00000000 ebx 5e47dbb4 ecx 00000000 edx 47900019 
I / DEBUG (115): esi 57a8ed84 edi bfb0eb78 
I / DEBUG (115): xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b 
I / DEBUG (115): eip 5e47a021 ebp bfb0eb98 esp bfb0eb20 flags 00010216 
  I / DEBUG (115): # 00 eip: 00003021 / data / data / com.example.apis / lib / libSampleJNIBinder.so   
I / DEBUG (115): # 01 eip: 0007a959 / system / lib / libdvm.so (_Z16dvmCallJNIMethodPKjP6JValuePK6MethodP6Thread +0 x1e9) 

The red part is wrong. So file,
eip: 00003021 is the wrong address, I need to find the error.



Heroes through online methods, can now be solved.
I wrote in my blog there: http://blog.csdn.net/oldmtn/article/details/8889654

Is the adb logcat output directly wrong location:
I get the following results:

 ********** Crash dump: ********** 
Build fingerprint: 'intel/mfld_dv10/mfld_dv10: 4.0.4/IMM76D/release.20130301: eng / dev-keys' 
pid: 3871, tid: 3871 >>> com.example.apis <<<< br />signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000 
Stack frame # 00 eip: 00003021 / data / data / com.example.apis / lib / libSampleJNIBinder.so: Routine Java_com_example_apis_JNI_SampleJNIBinder_JTCGetStringFromJNI in / home / huanghao / workspace_android / HHDemos / jni / SampleJNIBinder / SampleJNIBinder.cpp: 35 

< br />
However, this method is cumbersome. . . . . .


What easier way?

Hope to start a discussion. . . .

<-! Baidu Button BEGIN -> more Share to: <-! Baidu Button END ->

<-! Main posts under Banner (D4) -><-! Posts under the main text (D5) ->
Reply:
Such a good discussion of the post, did not even?
Reply:
I am dizzy, my big halo.
Eventually resolved themselves, thank you CSDN give me a chance here to make my question. . . . . . . . . . .
Reply:
Really good