On 11/25/2010 04:32 PM, Michal Nowak wrote:
----- "Jiri Moskovcak"jmoskovc@redhat.com wrote:
A new version [...]
When using what's in git now I crash some app and abrt will notice it, with this "new version" files it just ends like this
abrtd: FIONREAD:48 abrtd: FIONREAD:48 abrtd: FIONREAD:48 abrtd: Directory 'ccpp-1290698502-15420' creation detected abrtd: Locked '/var/spool/abrt/ccpp-1290698502-15420.lock' abrtd: Unlocked '/var/spool/abrt/ccpp-1290698502-15420.lock' 'brtd: run_event: line 'EVENT=post-create abrt-action-save-package-data 'brtd: Executing 'abrt-action-save-package-data abrtd: Executing: /bin/sh -c abrt-action-save-package-data : command not foundt-action-save-package-data abrtd: Corrupted or bad crash /var/spool/abrt/ccpp-1290698502-15420 (res:2), deleting abrtd: Locked '/var/spool/abrt/ccpp-1290698502-15420.lock' abrtd: Unlocked '/var/spool/abrt/ccpp-1290698502-15420.lock' abrtd: FIONREAD:48 abrtd: Got signal 17 through signal pipe
In /var/log/messages I can see just
abrtd: Corrupted or bad crash /var/spool/abrt/ccpp-1290698421-15362 (res:2), deleting
Some string handling problem in the new script?
I don't think it's caused by the new di-install script, I really don't see how the spawned child process could break the daemon that way..
Denys, any idea?
Michal _______________________________________________ Crash-catcher mailing list Crash-catcher@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/crash-catcher