I just updated guide for debugging pcmanfm on the wiki.
http://wiki.lxde.org/en/LXDE:PCManFM_build_and_setup_guide#Bug_Reporting_and_How_to_Help_Debug_PCManFM
A tip not previously mentioned was added.
Before you run the programs with gdb, do this:
export G_DEBUG=fatal-criticals
export G_SLICE=debug-blocks
This can turn on additional debugging facilities built into glib itself.
export G_SLICE=debug-blocks helps debugging memory allocation errors.
If you're using some other memory checker, such as valgrind, you can do
this:
export G_SLICE=always-malloc
This help you find out some more cryptic memory errors.
Next time, when you're debugging LXDE programs, please try to export these
environment variables to get more information.
For people who don't know how to use gdb, try to use its GUI frontend,
nemiver. I personally use this one and find it very handy and easy to use.
Thanks a lot.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Pcmanfm-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pcmanfm-develop
