public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Kunal Chauhan <atkunalchauhan@gmail.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb@sourceware.org
Subject: Re: Help: debug binary
Date: Wed, 13 May 2020 02:37:47 +0530	[thread overview]
Message-ID: <CACEFAc1Fsa04Qdi4i5wrFO5YGEgSCmzh_ZEaQcmixwE22a7CyQ@mail.gmail.com> (raw)
In-Reply-To: <20200512202240.GC2242921@embecosm.com>

Is gdb binary core.file   this can be run or developement system ? Means is
it necessary to run on target board

On 13 May 2020 1:52 a.m., "Andrew Burgess" <andrew.burgess@embecosm.com>
wrote:

> * Kunal Chauhan via Gdb <gdb@sourceware.org> [2020-05-13 01:05:32 +0530]:
>
> > Hi Team
> > As I am new to core files and gdb
> > >> How core file looks like in unix ?
> > >>Can we use gdb to findout crash from core files? at development
> > system.
>
> You don't really need to know the details of the core file format, you
> just need the core file and the corresponding binary and you can debug
> this with GDB.  See:
>
>   https://sourceware.org/gdb/current/onlinedocs/gdb/
> Invoking-GDB.html#Invoking-GDB
>
> Basically you want:
>
>   $ gdb application.exe core.file
>
> Then you should be able to investigate the state of the target at the
> time it produced the core file.
>
> Good luck,
> Andrew
>
>
>
>
> >
> > On Tue, May 12, 2020 at 8:54 AM Kunal Chauhan <atkunalchauhan@gmail.com>
> > wrote:
> >
> > > Hi Team
> > >
> > > I am new to the stuff of debugging and do not know any memory tools.
> > >
> > > 1. I have logs of binary and have only development machine. I searched
> my
> > > logs and prints shows something like.
> > >
> > > Void f1()
> > > {
> > >     F1()
> > >
> > > }
> > >
> > > 1.F1: returns the int val and after that binary crash .
> > > 2. In f1 some memory allocation and deallocation done for char*
> > >
> > >
> > > How can i check that particular function and file for memory crash .
> As i
> > > have develoment system where i can only compile my binary.?
> > >
> > > Please suggest some useful steps
> > >
> > >
> > > Thanks
> > > Kunal
> > >
> > >
> > >
> >
> > --
> > *Thanks with Regards!*
> >
> > *Kunal Chauhan*
> > *Mob:09813614826*
> > *Mob:08860397903*
> >
> > *E-mail:atkunalchauhan@gmail.com <E-mail%3Aatkunalchauhan@gmail.com>*
>

  reply	other threads:[~2020-05-12 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACEFAc0rQ2XJ0vgDb95AO0684eU+woBKAf84Z5Yhf1LFQ3dS5Q@mail.gmail.com>
     [not found] ` <CACEFAc24agH+OCFWqCf2rEUSEQxJSmK58dWt0z=3A2e=WAkhWA@mail.gmail.com>
     [not found]   ` <CACEFAc0C9J-x8_3H_3omD_-KBcgwqAR3Nd4q+JRaOpnvnPhybQ@mail.gmail.com>
2020-05-12  3:24     ` Kunal Chauhan
2020-05-12 19:35       ` Kunal Chauhan
2020-05-12 20:22         ` Andrew Burgess
2020-05-12 21:07           ` Kunal Chauhan [this message]
2020-05-12 21:35             ` Andrew Burgess

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=CACEFAc1Fsa04Qdi4i5wrFO5YGEgSCmzh_ZEaQcmixwE22a7CyQ@mail.gmail.com \
    --to=atkunalchauhan@gmail.com \
    --cc=andrew.burgess@embecosm.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).