On Thu, Sep 12, 2002 at 03:29:00AM +0200, Wolfgang Pfeiffer wrote: > On Sep 8, 2002, 19:55 (-0000) Mikhael Goikhman wrote: > > > On 08 Sep 2002 21:38:20 +0200, Wolfgang Pfeiffer wrote: > > > > > > On Sep 8, 2002, 18:59 (-0000) Mikhael Goikhman wrote: > > > > > > > On 08 Sep 2002 20:43:02 +0200, Wolfgang Pfeiffer wrote: > > > > > > > > > > On Sep 8, 2002, 08:51 (-0000) Mikhael Goikhman wrote: > > > > > > > > > > > Can you reproduce the crash with this two line .xinirc: > > > > > > > > > > > > xterm -geometry 92x50+1550+60 -e /usr/bin/pine & > > > > > > /usr/bin/fvwm -cmd 'AddToFunc StartFunction I FvwmPager' > > > > > > > > > > these 2 lines when starting fvwm or fvwm-themes-start ? > > > > > > > > The second line already starts fvwm in foreground, don't put any other > > > > lines into ~/.xinitrc except for maybe "sleep 3" in the middle. > > > > > > The same as with the old .xinitrc: XCrash if I type a 'q' on Pine in > > > an xterm > > > > So this happens with no config at all. Fine. Forget fvwm-themes for now. > > > > Please recompile 2.5.3 from sources and install it (say into /usr/local). > > Then run the same 2 line .xinitrc, but with /usr/local/bin/fvwm instead. > > When you get core, run "gdb /usr/local/bin/fvwm core" and then "where". > > Send the stack trace (5-20 lines), preferably to [EMAIL PROTECTED] > > Thank you very much. > > > > Regards, > > Mikhael. > > OK: I installed FVWM from source to the default directories with: > ./configure > make > make check (not being sure whether this was useful .. :) > make install > > I didn't touch any config.files for the build: just ran the 4 commands > from above. Didn't even install fribidi from source (tho there is > fribidi installed from an RPM ...) > > then running: > > ########################################### [snip] > #0 0x80a590c in FlocaleFreeNameProperty (ptext=0x80effe8) at > Flocale.c:1569 > #1 0x8074355 in free_window_names (fw=0x80effe0, nukename=0, > nukeicon=1) > at add_window.c:2812 > #2 0x8072651 in destroy_icon (fw=0x80effe0) at add_window.c:1255 > #3 0x80744bd in destroy_window (fw=0x80effe0) at add_window.c:2915 > #4 0x8070141 in HandleUnmapNotify () at events.c:3228 > #5 0x80703a1 in DispatchEvent (preserve_Fw=0) at events.c:3358 > #6 0x8070432 in HandleEvents () at events.c:3413 > #7 0x808398a in main (argc=3, argv=0xbffffa64) at fvwm.c:2251 > (gdb) > > ##############################################
The DeferExecution() function is trashing memory. I ran into the same problem yesterday and have hopefully fixed it in current CVS. (But be aware that fvwm will probably crash anyway.) Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
