top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

GDB: How to debug corrupted stack ?

+1 vote
GDB: How to debug corrupted stack ?
posted May 15, 2016 by Neeraj Mishra

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

0 votes

I don't think so there is a single command to debug the corrupted stack.
I used following set of commands while debugging issues.
$ bt /* for back trace ; which shows me the order of stack being called; */
$ p /* use to print value of a variable */
$ fr /* use to debug within the stack */

answer May 17, 2016 by Harshita
Similar Questions
+1 vote

I am working on some JIT compiler and I am using GDB to debut it, my code crashes at some point (segment fault), but it crashes at the jitted code (they are generated on the fly) so I do not get the stack frame information, But I got the following backtrace:

#0 0x**********d98f22 in ?? () // JITTED CODE
#1 0x000000000000001d in ?? () // JITTED CODE
#2 ...callattribuite function....

I am wondering if it is possible for GDB to disassemble the code at location 0x**********d98f22 and display it to me. I tried disas 0x**********d98f22 but GDB complained No function contains specified address.

Any clue?