On Sun, Dec 04, 2016 at 05:33:52PM +0000, Ken Moffat wrote: > On Sun, Dec 04, 2016 at 12:10:44PM +0100, Pierre Labastie wrote: > > >> > > Have you tried valgrind? > > > > That was suggested - but that system is already very close to 100% > full (even with /opt packages moved to a different partition), which > is why I decided to use a different system. That one was only > partly-built. I built lxdm, then realised that I needed lxsession to > replicate the setup. Too many missing deps, built next chunk of my > standard desktop but haven't yet got back to lxde. > Tried and failed - no memory leaks, no errors. I tried running it from a graphic term, to see what would happen. Got a black screen, then the desktop reappeared.
Log shows ==11921== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==11921== /path/to/gdb /usr/sbin/lxdm-binary ==11921== and then give GDB the following command ==11921== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=11921 ==11921== --pid is optional if only one valgrind process is running ==11921== So I tried it again - by preparing command lines on two ttys (as root) for valgrind and for gdb - without the --pid. First time, gdb didn't seem to like the ../../ (no such file for vgdb) so tried again specifying /usr/bin/vgdb. Also tried starting gdb (to load the symbols) first. But whatever I do, lxdm-binary seems to have already died before I get to gdb. For me, debugging X or even just desktop programs is a mystery. ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
