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@xxxxxxxxx> wrote: > On Tue, 5 May 2020 at 12:23, Kunal Chauhan <atkunalchauhan@xxxxxxxxx> > 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@xxxxxxxxx> > wrote: > >> > >> On Wed, 29 Apr 2020 at 18:23, Kunal Chauhan via Gcc-help > >> <gcc-help@xxxxxxxxxxx> 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@xxxxxxxxx > > > -- *Thanks with Regards!* *Kunal Chauhan* *Mob:09813614826* *Mob:08860397903* *E-mail:atkunalchauhan@xxxxxxxxx <E-mail%3Aatkunalchauhan@xxxxxxxxx>*
