Using gdb-xfreemod 6.0 instead of gdb-xfreemod 5.11-2.0 , I could use gdb to debug XFree86 430 under redhat 9.0.
Following is the way what i am using. Using attach process ID after Xwindow had running, still could not break during what i setted breakpoints. But direct debug XFree86 "gdb /usr/X11R6/bin/XFree86" then "run :0",could certainty break at breakpoints. Thanks for suggest Harry ----- Original Message ----- From: "Alex Deucher" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 30, 2003 1:21 AM Subject: Re: Help: gdb xfree86 video card driver on rh9 > try one of these module enabled versions of gdb: > > http://www.logix.cz/michal/devel/gdb-xfreemod/ > http://www.dawa.demon.co.uk/xfree-gdb/ > > Alex > > --- Thomas Winischhofer <[EMAIL PROTECTED]> wrote: > > harry wrote: > > > > > I am debuging a video card driver on XFree86.I was using gdb > > > 5.1.1-2.0xfree on radhat 9.0. And I had tried : > > > (1) I was using "gdb /usr/X11R6/bin/XFree86" , then run. It result > > as > > > "Segmentation fault". > > > (2) During build sis_drv.o, I had using para "-g" for gcc. > > > "startx" open Xwindow fristly, then using "ps ax" gets the > > processid > > > of "X :0". > > > use SSH login > > > and "gdb /usr/X11R6/lib/modules/drivers/sis_drv.o processid". > > > By this way, i could see source codes and function symbols of the > > > sis_drv.o , and could set breakpoints. But Xwindow will not break > > at > > > those points that i setted.What's wrong on my ways to debug video > > driver > > > of xfree86 bu gdb? > > > > > > Now i only could use print message to debug,but that is > > troublesome. > > > If anybody has some suggestion as how to debug I would gladly > > > appreciate any suggestions. > > > > Nice to see that a SiS employee is dealing with XFree86. > > > > I am no gdb expert myself, but here is my $.02: > > > > 1) You need a patched gdb which is capable of dealing with XFree86's > > modules. I don't have a link at hand, but I'm sure someone else > > reading > > this has. > > > > 2) If you want to attach to the running XFree86 process: sis_drv.o is > > not the process, but part of the X process. You need to attach to the > > X > > process. > > > > In case you are "debugging" the official XFree86 sis driver, I'd > > appreciate if you told me what problems you experience (since I am > > the > > author and maintainer of this driver). > > > > Thomas > > > > -- > > Thomas Winischhofer > > Vienna/Austria > > thomas AT winischhofer DOT net *** > > http://www.winischhofer.net/ > > twini AT xfree86 DOT org > > > > > > > > _______________________________________________ > > Devel mailing list > > [EMAIL PROTECTED] > > http://XFree86.Org/mailman/listinfo/devel > > > __________________________________ > Do you Yahoo!? > New Yahoo! Photos - easier uploading and sharing. > http://photos.yahoo.com/ > _______________________________________________ > Devel mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/devel _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
