Comment 8 for bug 620278

Hello,

So, here is my report - not exactly the one we assumed : however :

last friday evening, reading briefly the doc, I understood that attaching gdb to X was dead simple, so I tried - and X froze - completely - it was late, thus I dropped it, and resumed the debug session now.

It kept freezing. meanwhile, looking closely to the situation, I noticed that the doc mentions attaching to /usr/bin/Xorg; however, on my Ubuntu 10.04 (I have two desktops at home, one x86_64 and one i686), ps -ef|grep X shows /usr/bin/X running, not /usr/bin/Xorg; I verified more closely :

/usr/bin/X is brought by xserver-xorg, which claims :

" This package depends on the full suite of the server and drivers for the
 X.Org X server. It does not provide the actual server itself."

Really ?

whereas /usr/bin/Xorg is brought by xserver-xorg-core : and we have xserver-xorg-core-dbg, but no xserver-xorg-dbg, which can explain why, before freezing X, gdb claimed it found no symbols when attaching to X ...

comparing X and Xorg :

-rwsr-sr-x 1 root root 10,520 2010-04-09 04:07 /usr/bin/X
-rwxr-xr-x 1 root root 1,901,280 2010-07-21 15:08 /usr/bin/Xorg

two completely different executables : one with the sticky bit set, and so tiny !

This situation looks messy : don't you think ?

I just connected through VPN at work : on CentOS 5.5, it's definitely /usr/bin/Xorg - which seems consistent with today's fashion (I am an old timer, remember ? I knew X11R6 on HP-UX and SunOS, not to mention Solaris)

just to give it a try, in /etc/kde4/kdm/kdmrc, I replaced

ServerCmd=/usr/bin/X

with

ServerCmd=/usr/bin/Xorg

and restartedkdm