Re: Help: debug binary

[Andrew Burgess <andrew.burgess@embecosm.com>]

* 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>*