I haven’t done a huge amount of debugging without source-code available. That’s the part of the Adobe Reader binary that is causing the crash. 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! Install Adobe Acrobat Reader on Ubuntu 20. Adobe Reader Ubuntu with examples on files, directories, permission, backup, ls, man, pwd, cd, linux, linux introduction, chmod, man, shell, pipes, filters. This seems to be something of an ongoing problem in Linux, not just with this setup. 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. In most applications I have no option of printer language, and in the ones which I do (namely acroread) it makes no difference. 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. While there is still quite a ways to go, commercial support for the Linux. (Or bt full, for a complete back-trace). View PDFs within your web browser with the official Acrobat Reader plug-in. Usually after a program has crashed in gdb you’d issue the bt command to get a back-trace.

Acroread linux