Menu editor crashes when I try to open /usr/lib

[TerryJ]

Erik Harrison wrote:
> On 1/20/07, TerryJ <listmail at exemail.com.au> wrote:
>   
>> Álvaro Lopes wrote:
>>     
>>> TerryJ wrote:
>>>
>>>       
>>>> Jean-François Wauthy wrote:
>>>>
>>>>         
>>>>> On Sat, 2007-01-20 at 10:35 +1100, TerryJ wrote:
>>>>>
>>>>>
>>>>>           
>>>>>> There was no appearance of the editor in each case.  I conclude that gdb
>>>>>> cannot run the xfce menu editor. =-O
>>>>>>
>>>>>>
>>>>>>             
>>>>> Oh yes it can :p
>>>>>
>>>>> use gdb xfce4-menueditor as command
>>>>>
>>>>> (gdb) run
>>>>>
>>>>> wait for a crash (or not :)), if it crashes
>>>>> (gdb) bt
>>>>>
>>>>> HTH
>>>>>
>>>>>           
>>>> This sort of thing is all in a day's work for you, I suppose.  My
>>>> interpretation of your message and the results follow:
>>>>
>>>> - - - quote - - -
>>>> [terry at localhost xfl]$ gdb xfce4-menueditor
>>>> <snip>
>>>> (no debugging symbols found)
>>>> Using host libthread_db library "/lib/i686/libthread_db.so.1".
>>>>
>>>> (gdb) run
>>>> Starting program: /usr/bin/xfce4-menueditor
>>>>
>>>> [2]+  Stopped                 gdb xfce4-menueditor
>>>> - - - end quote - - -
>>>>
>>>> <snip>
>>> Try launching the menu editor normally. Then, before you open /usr/lib, open a xfterm:
>>>
>>> Get the PID of the xfce4-menueditor: "pidof xfce4-menueditor" or "ps xau| grep xfce4-menueditor".
>>>
>>> Launch gdb, and write "attach PID", where PID is the xfce4-menueditor pid. Then issue the command "cont".
>>>
>>> Open "/usr/lib" and watch the errors in gdb (see [2]). Issue a backtrace.
>>>
>>> Send us the backtrace.
>>>
>>>
>>>
>>>
>>> Example:
>>>
>>> <snip>
>>>       
>> Ok.  I'll do that.  Meantime, I closed the terminal because I wanted to
>> edit the bash history files.  Two menu-editor windows appeared from
>> nowhere, so I opened the terminal again and :
>>
>> - - - quote - - -
>> <snip>
>>
>> I watched the hour glass turning for 2 minutes and killed the menu editor.
>>     
>
> Yeah, ignore that.You crashed the app, gdb is keeping the OS from
> cleaning up the crashed application so that you can issue it commands
> to probe the applications state. If it closed, gdb can't get any info
> out of it.

Right.  I have just repeated the exercise but the result is no more 
informative:

Program received signal SIGSEGV, Segmentation fault.
0xa759246a in strcmp () from /lib/i686/libc.so.6
(gdb) bt
#0  0xa759246a in strcmp () from /lib/i686/libc.so.6
(gdb)

The hour glass is still turning. :-\

-- 

Regards, TerryJ

Using Xfce on PCLinuxOS. www.revivalcentres.org