Hi Vit,
I'd rather use 'Ruby' as value of the analyzer field. If the analyzer field is
set to 'Python' the ABRT believes that the backtrace field contains a python
backtrace. A new analyzer/type needs a proper configuration of events,
therefore I prepared a patch that changes the analyzer value to 'Ruby' and
adds a configuration file.
(I changed rubygem-abrt.spec because the configuration file must be installed
to /etc/libreport/events.d/).
The patches are attached.
Regards
Jakub
On Monday 09 of July 2012 15:47:51 Vít Ondruch wrote:
Hi,
Updated ABRT gem version 0.0.2 is available at
RubyGems.org if you like
to test it. I'd love to hear some feedback.
There were done following changes:
* Improved code base
* Better handling of some edge cases, such as call to Kernel#exit or
Ctrl+C event
* Test suite added
* Improved documentation
I also prepared RPM for Fedora. Review is available at
https://bugzilla.redhat.com/show_bug.cgi?id=838568
Vit