On Sun, May 26, 2002 at 10:37:05PM -0400, Thomas Gardiner wrote:
> Hi,
>
> On Sun, 26 May 2002, Dominik Vogt wrote:
>
> > On Thu, May 23, 2002 at 05:07:39PM -0400, Thomas Gardiner wrote:
> > > Hi,
> > >
> > > I mannaged to get fvwm to hang the X display today and thought maybe
> > > someone out there might have an idea why.
> > >
> > > Using fvwm2 version 2.4.7 I started gcalc. There is a gutton next to the
> > > "File, Edit, Help" Menu bar. After left clicking on it, one can drag it
> > > off into it's own window.
> > >
> > > I noticed that it was slow in redrawing the area behind it after movement
> > > and yanked it around kind of fast.
> >
> > Are you *sure* you saw this with 2.4.7 and not 2.5.x? I can't
> > reproduce it with 2.4.7, and in the latest 2.5.x code, the slow
> > movement with gtk widgets is already gone.
(... and the bug was introduced in 2.5.x)
> Yes, I'm sure it is 2.4.7. I downloaded and built it myself. It is a
> local (to my home directory) installation, but I'm sure that the correct
> executeable is being called as well. If it's of any help, I can find out
> the particulars of the version of gcalc and Linux distro. (Mandrake ...).
The gtk version is what matters.
> Is it possible that the Fvwm error was caused in part by me?
The error message comes from the module interface. When the
machine is too busy and module messages are not processed for too
long, the module is killed. It usually happens with FvwmEvent
because it's the most active module.
> I remember
> gcalc hanging and not being redrawn. I then chose to kill it by switching
> to a virtual terminal. As I recall, before killing it, gcalc had a good
> chunck of the cpu (X had the rest). After killing it fvwm started
> gobbling up the cpu. I didn't check for the fvwm error until after I
> noticed fvwm taking up a bunch of the cpu cycles.
When that happens again, could you try to attach a debugger and
see where fvwm is looping? To do this, exit to the console, find
out fvwm's process id with
$ ps -ax | grep fvwm2
and attach gdb to the running fvwm:
$ gdb fvwm2 <process-id>
Then fetch a stack trace from gdb
(gdb) where
and post it. You might find out more by single stepping through
the code with the "step" command on the gdb prompt.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, email: d.vogt_at_lifebits.de
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
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 May 27 2002 - 05:14:10 BST