oppa@oppa-hex-ssd:~$ pdfchain
PDF Chain 0.4.4.2 - A graphical user interface for the PDF Toolkit
Segmentation fault
(gdb) run
Starting program: /usr/bin/pdfchain
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea4fe700 (LWP 16794)]
[New Thread 0x7fffe9cfd700 (LWP 16795)]
PDF Chain 0.4.4.2 - A graphical user interface for the PDF Toolkit
[New Thread 0x7fffe3fff700 (LWP 16797)]
[New Thread 0x7fffe36eb700 (LWP 16798)]
[New Thread 0x7fffe2c97700 (LWP 16800)]
Thread 1 "pdfchain" received signal SIGSEGV, Segmentation fault.
0x00007ffff4af9360 in g_slist_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
An alternative might be: file a bug
I think pdfsam could do the same job
pdftk file1 file2 fileN cat output outputfilename
~$ strace -eopen pdfchain
strace -eopen pdfchain | grep WHAT
?The strace will stop as soon as the segfault happens, so hopefully the culprit will be opened near the end.