LINUX ask a question! Then lines. . . . . . . . I would like to documents generated by core debugging, implementation #gdb Core Ones (Gdb) # 0x00011000 in : () Function who do not see, do not know how else do not know can not be address "0x00011000" to function name? LINUX ask a question! Then lines. . . . . . . . Sink so quickly that no one knows? LINUX ask a question! Then lines. . . . . . . . Zaiding that you can return expectations! . . . . . . LINUX ask a question! Then lines. . . . . . . . Can you confirm your debugging information contained in the document? LINUX ask a question! Then lines. . . . . . . . This parameter is not necessary -core=file time, I remember to enter gdb debugging core documents previously only read this information, you try the bar LINUX ask a question! Then lines. . . . . . . . I have added a debugging information gcc-g xx.c LINUX ask a question! Then lines. . . . . . . . First you must increase g to generate executable files, then find a core document, and order : Core.xxxx /yourpath/yourexe LINUX will be able to perform the [ Closed window ]