I haven’t done a huge amount of debugging without source-code available.

But until recently, you could at least download and install Reader on your Linux desktop machine. This should come as no surprise, as the last time Adobe Reader for Linux was updated came in May 2013. That’s the part of the Adobe Reader binary that is causing the crash. Adobe has pulled the plug on supporting its PDF reader app for Linux. Download Adobe Reader 9.5 for Linux from. It is initially available in the paid and free versions. It is really silly, they should ban these XFA forms or at least replace the Please Wait with the non-fillable version. It also allows doing all necessary tasks on your pdf files. However, Acrobat Reader is widely used as a full package PDF viewer. Acrobat Reader is Adobe’s official PDF reader app, and now it works on Linux smoothly. 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. Almost all the users are familiar with the name Adobe. 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). It’s a free program that you can download from the Adobe website. Usually after a program has crashed in gdb you’d issue the bt command to get a back-trace. The Linux version of Adobe Acrobat Reader is called Adobe Reader.

Adobe reader linux