From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Kunal Chauhan <atkunalchauhan@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: [Help/Hint]: gdb output analysis
Date: Thu, 14 May 2020 21:03:55 +0200 [thread overview]
Message-ID: <f4a4e515020ca85efb4e6f0a5d978b20f99ed731.camel@skynet.be> (raw)
In-Reply-To: <CACEFAc3iCLhRMLKCGcsr5gjzEfF48S1fiw3ap5zf7VgA+z1w8w@mail.gmail.com>
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.
Philippe
prev parent reply other threads:[~2020-05-14 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 13:36 Kunal Chauhan
2020-05-14 13:48 ` Philippe Waroquiers
2020-05-14 14:15 ` Kunal Chauhan
2020-05-14 19:03 ` Philippe Waroquiers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f4a4e515020ca85efb4e6f0a5d978b20f99ed731.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=atkunalchauhan@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).