[Help/Hint]: gdb output analysis
Kunal Chauhan
atkunalchauhan@gmail.com
Thu May 14 13:36:25 GMT 2020
Hi Team,
I got some output at gdb with core dump file
*I have not a clue that how the address shown by gdb can help me to go to
exact point of code violation.*
*please suggest some clue !*
*Logs by gdb:*
Core was generated by `/opt/proj/bin/ty 0 0'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xb66e8ee4 in strlen () from /lib/libc.so.6
[Current thread is 1 (LWP 2084)]
(gdb) bt
#0 0xb66e8ee4 in strlen () from /lib/libc.so.6
#1 0xb6da3854 in ?? () from /opt/qcom/lib/libcurl.so.4
#2 ---Type <return> to continue, or q <return> to quit---
thanks
kunal
More information about the Gdb
mailing list