Breakpad and linuxdeployqt

[ymiroshnyk]

Hi,

I try to use Breakpad to catch crashes in application bundled with linuxdeployqt. The idea is to build release binary with debugging symbols, save symbols, strip them from executable file and deploy to the user. If crash happens, Breakpad saves call stack and send a crash report to developer. Afterwards developer can use saved debugging symbols and crash report to find out human readable call stack to analyse the crash.

I found that after linuxdeployqt ran on executable, it apparently changed the file and debugging symbols become invalid and in most of cases I see wrong crash call stack. Can you confirm, that I can't rely on debugging symbols after linuxdeployqt? And if so, is it possible somehow to have correct debugging symbols after executable modified?

Thanks.

[probonopd]

I don't know enough about how debugging symbols work but I can confirm that linuxdeployqt uses patchelf to rewrite rpaths in executables and libraries.

[ymiroshnyk]

I opened a thread at patchelf forum regarding this.

[rodlie]

A workaround would be to set the RPATH when building the application to match ../lib, and don't use patchelf on your binary (is that possible in linuxdeployqt?).

I have experience with breakpad and older patchelf, used to work fine.