From: Kunal Chauhan <atkunalchauhan@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Help: debug a binary
Date: Tue, 5 May 2020 18:37:25 +0530 [thread overview]
Message-ID: <CACEFAc23Ep2Hm92EiAFNqGazEUd20MjHdVv-ZAgfmMUqXskgYA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdR8F7d_NC81zmWZrVg6pDzA-qG9r9ncOXo9Bn1zarKzOQ@mail.gmail.com>
Thanks ! for pointers towards topic
I will separate the GDB discussion from here .! ; Will only use GCC
discussion here
On Tue, May 5, 2020 at 6:23 PM Jonathan Wakely <jwakely.gcc@gmail.com>
wrote:
> On Tue, 5 May 2020 at 12:23, Kunal Chauhan <atkunalchauhan@gmail.com>
> wrote:
> >
> > Hi Team,
>
> This is the mailing list for GCC, not GDB. Questions about how to use
> GDB or what GDB messages mean are off-topic here.
>
> >
> > Help for finding and understanding the below line coming in gdb : what
> exactly they are saying ?
>
> Looks like it's saying that your program's stack looks corrupt. You
> probably have a memory corruption bug. Try using valgrind to run it,
> or recompile with -fsanitize=undefined and/or -fsanitize=address and
> see if they report errors when you run it.
>
> >
> > #0 0xb66e8ee4 in strlen () from /lib/libc.so.6
> >
> > [Current thread is 1 (LWP 2084)]
> >
> > (gdb) bt full
> >
> > #0 0xb66e8ee4 in strlen () from /lib/libc.so.6
> >
> > No symbol table info available.
> >
> > #1 0xb6da3854 in ?? () from /opt/qcom/lib/libcurl.so.4
> >
> > No symbol table info available.
> >
> > #2 0x05b40000 in ?? ()
> >
> > No symbol table info available.
> >
> > Backtrace stopped: previous frame identical to this frame (corrupt
> stack?)
> >
> >
> > On Wed, Apr 29, 2020 at 11:21 PM Jonathan Wakely <jwakely.gcc@gmail.com>
> wrote:
> >>
> >> On Wed, 29 Apr 2020 at 18:23, Kunal Chauhan via Gcc-help
> >> <gcc-help@gcc.gnu.org> wrote:
> >> >
> >> > Hi team,
> >> >
> >> > How can I debug my binary.
> >>
> >> Compile with the -g flag and use a debugger.
> >>
> >> Search the web for "using gdb".
> >
> >
> >
> > --
> > Thanks with Regards!
> >
> > Kunal Chauhan
> > Mob:09813614826
> > Mob:08860397903
> > E-mail:atkunalchauhan@gmail.com
> >
>
--
*Thanks with Regards!*
*Kunal Chauhan*
*Mob:09813614826*
*Mob:08860397903*
*E-mail:atkunalchauhan@gmail.com <E-mail%3Aatkunalchauhan@gmail.com>*
prev parent reply other threads:[~2020-05-05 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 16:16 Kunal Chauhan
2020-04-29 17:51 ` Jonathan Wakely
2020-05-05 11:22 ` Kunal Chauhan
2020-05-05 12:53 ` Jonathan Wakely
2020-05-05 13:07 ` Kunal Chauhan [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=CACEFAc23Ep2Hm92EiAFNqGazEUd20MjHdVv-ZAgfmMUqXskgYA@mail.gmail.com \
--to=atkunalchauhan@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).