[Help/Hint]: gdb output analysis

Philippe Waroquiers philippe.waroquiers@skynet.be
Thu May 14 19:03:55 GMT 2020

On Thu, 2020-05-14 at 19:45 +0530, Kunal Chauhan wrote:
> Hi  
> I have only binary and core file at running the gdb only
> will bt full is not working it showing following
> >>>>> : previous frame is identical ,
> >>also when i tried : return it shows , it will need the process, should I need the process to run , but scenerio of crash I can not produce.
> Steps that I followed as below:
> > gdb process core file
> output:
>     0xb66e8ee4 in strlen () from /lib/libc.so.6
> > #1  0xb6da3854 in ?? () from /opt/qcom/lib/libcurl.so.4
> > #2  ---Type <return> to continue, or q <return> to quit-- 
> >bt full
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> (gdb 
Then it will be painful :(.
You might try to guess what went wrong in the stack, and then
using e.g. 'frame address STACK-ADDRESS' if you can locate
a previous correct frame address.

I am sorry I will not be able to help more on that.


More information about the Gdb mailing list