abrt 1.0.9 detected a crash.
Attached file: backtrace
reason: Process /usr/bin/ballz was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Created attachment 410233 [details]
Thanks for the bug report.
Looking at the backtrace you send a sigterm (signal 15) to ballz in some way (maybe you closed the terminal from which you started it, or you were logging out?), which got intercepted by allegro (the gaming library ballz) uses and then turned into an abort which got intercepted by abrt.
Doing an abort is allegro's standard behaviour when an allegro using game is not exited cleanly, so I don't consider this a bug.