I haven’t done a huge amount of debugging without source-code available. It can be installed on Ubuntu Linux by downloading its deb package and APT package. It’s a free program that you can download from the Adobe website. Un buen ejemplo es el Foxit Reader, un lector de PDF bastante popular, que ha llegado a ser comparado a la par de Adobe Reader, pero este que es más ligero que Adobe Reader y tiene características similares, pero mejores, incluyendo un excelente soporte para la reproducción de grandes documentos PDF. Adobe Acrobat Reader is a powerful utility to read and print PDF files. That’s the part of the Adobe Reader binary that is causing the crash. The Linux version of Adobe Acrobat Reader is called Adobe Reader. So it looks like a memory allocation error that is causing a segmentation fault.īut if you look at the call stack, you’ll need to find the last stack frame that references Adobe Reader. The crash is occurring in a call to memset in the Visual C++ runtime. ![]() ![]() So debugging the problem isn’t going to be easy! However, as the application is Adobe reader AND the crash appears to be occurring in the visual studio C++ runtime AND you don’t have the source code to either of those binaries, you’re going to be dealing purely with assembly/machine code. ![]() Then you can see the call stack at the time of the crash and investigate the state of the stack frames and the variables inside. (Or bt full, for a complete back-trace). Usually after a program has crashed in gdb you’d issue the bt command to get a back-trace.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |