Re: ANNOUNCE: Verve 0.1.0 - A panel command line plugin

Jasper Huijsmans <[email protected]> Sat, 11 Feb 2006 22:24:47 +0100
Newsgroups gmane.comp.desktop.xfce.goodies.devel
Message-ID <[email protected]>
Jannis Pohlmann schreef:
> On Sat, 11 Feb 2006 17:59:34 +0100
> Jasper Huijsmans <[email protected]> wrote:
> 
>> Jannis Pohlmann schreef:
>>> On Sat, 11 Feb 2006 17:00:50 +0100
>>> Jasper Huijsmans <[email protected]> wrote:
>>>
>>>> Jannis Pohlmann schreef:
>>>>> On Sat, 11 Feb 2006 23:50:04 +0900
>>>>> Daichi Kawahata <[email protected]> wrote:
>>>>>
>>>>>> On Sat, 11 Feb 2006 23:39:04 +0900
>>>>>> Daichi Kawahata wrote:
>>>>>>
>>>>>>> Verve causes segfault against the xfce4-panel 4.3.28
>>>>>> No, it was a bus error actually on IRIX 6.5 (big endian)
>>>>>> by verve-plugin 0.1.0 (rev. 1030).
>>>>> So it's not due to a problem in the verve-plugin?
>>>>>
>>>> Why is this an internal plugin? Plugins should be external unless
>>>> there is a very good reason for it not to be. I specifically
>>>> created this possibility so that plugins would not crash the
>>>> panel :(
>>> I remember having trouble with gaining the keyboard focus of the
>>> command line input field when compiling it as an external plugin.
>>> Anyway, I can understand this concept and tried to apply your patch.
>>> It's properly installed and such, but once you want to add it to the
>>> panel, there is a CRITICAL message in the panel log and the plugin
>>> is removed again. Can you please look into that or tell me how to
>>> get more descriptive logs?
>> Hmm, it works fine for me. What is the message exactly?
> 
> ** (xfce4-panel:4182): CRITICAL **: Ein Item wurde unerwartet entfernt:
> "Verve-Kommandozeile".

Well, it basically means your plugin crashes. Maybe I have different 
libraries/dependencies installed, so my plugin may not trigger the crash.

I have to think about how to debug an external plugin properly. Hmm, it 
would be kinda cool to have 'xfce4-<name>-plugin --debug' which would 
run the plugin in a separate window...

	Jasper