Re: Nautilus debugging tips?

[Christian Schneider <c schneider scram de>]

Jimmy Do wrote:

> Hey everyone,
>
> Initially, one of the toughest things about contributing to Nautilus
> was learning how to debug effectively. I've developed a pattern of
> debugging that works for me, but I was wondering if anyone has any
> further advice.
>
> Right now, here's what I do:
> 1. find a bug
> 2. locate the part of the source where I suspect the bug might be
> 3. look through the code and understand its paths of execution
> 4. open up a terminal
> 5. run: 'ps axu | grep nautilus' to get Nautilus' pid
> 6. run: 'gdb nautilus <nautilus pid>' to debug the currently running
> nautilus process
> 7. debug by placing lots of breakpoints
> 8. edit the source code
> 9. compile & install the updated nautilus with 'make && make install'
> 10. restart nautilus: 'nautilus --quit'
> 11. repeat steps 5-10 until the bug is fixed
>
>  
One other step that will sure help in debugging.

Try

strace nautlius

It tells you all system calls. While this isn´t exactly a debugger it 
will give you a rough overview what the programm is doing.
I think tihs would be a nice step before running gdb.

--
greets

Christian Schneider

http://www.liquid-reality.de