Steve Goldman <sgoldman_at_gretch.East.Sun.COM> writes:
> steve.goldman_at_sun.com said:
> >
> > With fvwm 2.4.x I see the following strange behavior:
> >
> > 1: fvwm pager eventually disappears. It core dumps with following
> > traceback:
> >
> > [1] XTextWidth(0x780018, 0x37bf8, 0x6, 0x7efefeff, 0x81010100, 0xff00), a
> t 0xff231e00
>
> Since posting this I've done some more experiments. There had been some sugge
> stion
> that the problems noted above were due to problems in the Solaris X server. I
> could
> buy that but I did some more experiments. I went back and I rebuilt 2.0.46 wh
> ich I
> had been running with no problems on Solaris 8 and switched to it. All of the
> problems
> mentioned above have gone away and I've seen no bad behavior. So while it doe
> sn't
> exonerate the Solaris 9 X server it must surely be some clues. My next though
> t
> was that maybe this was triggered by some different configuration issue. Unfo
> rtunately
> the configuration between 2.0.46 and 2.4.x is so drastically different that a
> simple comparison doesn't seem productive. However I thought that maybe with
> the
> knowledge that 2.0.46 works properly and the symptoms above (especially #3) t
> hat
> maybe someone could give me a pointer as to what I could look and while tryin
> g
> to debug it since I'd like to use 2.4.x if I could.
I don't have 2.0.46 handy, but I do have 1.24r.
In that version there is no call to XTextWidth.
If you want to debug this, create a test program with a call to
XTextWidth. Use the logic in FvwmPager as a guide.
If you can get a test program to fail, you might have a chance
of convincing Sun there X server is broken or you might uncover
something in Fvwm.
--
Dan Espen E-mail: dane_at_mk.telcordia.com
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Mon Oct 20 2003 - 09:38:00 BST