ABRT for Ruby

Vít Ondruch vondruch at redhat.com
Tue Jul 17 14:30:11 UTC 2012


Hi Jakub,

Thank you for your patches. I have integrated them into v0.0.3 which is 
now available at RubyGems and as a SRPM in the review referenced earlier.

There also other news in this release:

* Exectubale name is extracted from backtrace, to prevent possible 
issues when $PROGRAM_NAME is modified in runtime.
* Oneline scripts and scripts executed from relative paths are ignored.
* Improved test suite.

And as always, feedback is appreciated.


Vit



Dne 10.7.2012 11:55, Jakub Filak napsal(a):
> 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




More information about the ruby-sig mailing list