Greetings again,
I should start by saying "thank you" to all of you who tried to help me the last time I dropped in here... quite a long time ago. I really did appreciate how much you all were willing to try to help me to transition from fvwm 1.24 to fvwm 2.xx, but ya know, some people just can't be helped. :-) But seriously, in the end it just came down to a matter of time. I just ran out of time to work on transitioning to fvwm 2.xx, and I managed, in the end, to hack my old .fvwmrc file around enough so that it would continue to do what I needed it to do (with fvwm-1.24), and as other tasks were pressing n me, I had to leave it at that. So anyway, I never did make that jump to fvwm 2.xx. Im still using fvwm-1.24. That situation perfectly acceptable to me, right up until recently, when I started trying to migrate myself from FreeBSD 7.0-RELEASE/i386 to 7.2-RELEASE/amd64. *Now* Ive got major trouble, and I'm in need of some friendly advice again. In a nutshell, I _have_ been able to build and install fvwm-1.24 onto FreeBSD 7.2-RELEASE/amd64 (from the FreeBSD ports tree), _however_ the resulting executable is behaving very badly indeed. It's using up 100% of the CPU time. Definitely bad, big time. So I want to try to run this thing under gdb, and see what (if anything) I can manage to puzzle out about why it may be pegging the CPU usage. This is where I get lost. I know real well how to use gdb on ``ordinary'' sorts of (text-output) programs, but I really have now idea how to run gdb on any sort of X11 application, must less on a window manager that's normally started out of my .xinitrc file. So could somebody here please pass me a clue? How does one use gdb to debug an X11 window manager? Where and how do you start gdb and the window manager? (I've really never even attempted anything even remotely like this before, so I'm just lost.) When answering, please assume that I've already managed to get fvwm compiled with -g (to include debugging info). I have. Thanks in advance for any help. Regards, rfg
