GDB shows more number of backtraces (90) for my core file

Question

GDB 7.7 shows more number of backtraces (90) for my core file. It is problem with GDB or core file or stack corruption issue?

(gdb) bt
Python Exception exceptions.ImportError No module named traceback: 
#0  0x00007f422fd04c37 in ?? () from /users/jegan/lib/x86_64-linux-gnu/libc.so.6
#1  0x0000000000002929 in ?? ()
#2  0x7328203c20746e63 in ?? ()
.......................
......................
#88 0x544143494649544e in ?? ()
#89 0x29295d305b4e4f49 in ?? ()
#90 0x0000000000000000 in ?? ()
(gdb)

Answer 1

GDB 7.7 shows more number of backtraces (90) for my core file.

There are a few likely causes for this:

1. You didn't invoke GDB correctly, or
2. You are analysing a core dump on a different host from the one it was produced on (or the same host has had its system libraries updated).

Answer for #1.
Answer for #2.