ABRT for Ruby

[Vít Ondruch]

Dne 13.7.2012 16:12, Vít Ondruch napsal(a):
> Dne 9.7.2012 22:46, KOSAKI Motohiro napsal(a):
>> On Mon, Jul 9, 2012 at 9:47 AM, Vít Ondruch <vondruch at redhat.com> 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
>>
>>>   def self.report(backtrace, io = abrt_socket)
>>>     io.write "PUT / HTTP/1.1\r\n\r\n"
>>>     io.write "PID=#{Process.pid}\0"
>>>     io.write "EXECUTABLE=#{$PROGRAM_NAME}\0"
>> Hmm..
>>
>> If I understand correctly, EXECUTABLE key is used for looking up 
>> package name
>> from abrt daemon. Then, It should be realfilename. See below abrt doc.
>>
>>
>> abrt/doc/interpreted-languages:
>>
>>> EXECUTABLE
>>> The file with the main entry point of the application. Might be a JAR
>>> archive, a script file, a bytecode file, or the interpreter. It should
>>> be a real file on the filesystem, so ABRT can check the origin of the
>>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>>
>> However, PROGRAM_NAME can be changed from ruby scripting. e.g.
>> $0 = "foobar"
>>
>
> The executable name is now always obtained from the backtrace:
>
> https://github.com/voxik/abrt-ruby/commit/8c5dbb9f4db3b6328a8945e0eff17b57c67d806c 
>
>
>

Sigh, I took the most straight-forward approach and missed this line 
https://github.com/voxik/abrt-ruby/blob/master/lib/abrt/handler.rb#L8

Vit