Hi !
i just can’t find if / where vanilla pd writes a crash log on an RPi (jessie) i am also very new to raspbian, so this might be very obvious?
i need to debug an unattended installation where pd crashes once in a while - usualy when i am not around. do i need to tell pd explicitly to write a crash log?
cheers! michael
On 2018-05-28 08:30, michael strohmann wrote:
Hi !
i just can’t find if / where vanilla pd writes a crash log on an RPi (jessie) i am also very new to raspbian, so this might be very obvious?
i need to debug an unattended installation where pd crashes once in a while - usualy when i am not around. do i need to tell pd explicitly to write a crash log?
Pd doesn't write anything like a crash log, not even on request. you'd have to do that manually.
the simplest way is to just redirect the stderr to a logfile: $ pd -stderr 2>pd-$(date +%s).log
this is of course not a real crash-log, as it will just record whatever is printed by Pd while it is operational. it might still help you finding the cause of the problem. also note, that depending on the verbosity this might grow quite big (if Pd does NOT crash within a reasonable time).
another (more sophisticated) option would be to enable core-dumps and inspect the one generated during the crash:
## enable core-dumps (in bash)
$ ulimit -c unlimited
## run Pd and wait till it crashes (creates a 'core' file)
$ pd CRASHPATCH.pd
## inspect the 'core' file generated by 'pd'
$ gdb pd core
(gdb) bt
fgsmd IOhannes