Rox-Filer crashes FVWM

In rox-filer renaming or moving file/s crashes fvwm, not all the time but here’s what I get when renaming a blank file from meow to moooooooo in rox-filer[code]gdb fvwm ~/core
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for details.
This GDB was configured as “x86_64-pc-linux-gnu”…(no debugging symbols found)
Using host libthread_db library “/lib/libthread_db.so.1”.

Core was generated by `fvwm’.
Program terminated with signal 11, Segmentation fault.
Cannot access memory at address 0x2b7be9a71968
#0 0x000000000044e580 in ?? ()
(gdb) where
#0 0x000000000044e580 in ?? ()
Cannot access memory at address 0x7fffc114d2f8[/code]

What version of FVWM did you say you were using? I note you’re running that on a 64-bit machine. If you’re not running FVWM 2.5.16, I suggest you try that to see if that alleviates this issue.

– Thomas Adam

fvwm --version fvwm 2.5.17 (from cvs) compiled on Jul 15 2006 at 00:08:51 with support for: ReadLine, Stroke, XPM, PNG, Shape, XShm, SM, XRender, XFT, NLS Using pierreg ebuild from here

PS - Sorry for late reply, been one crazy week :neutral_face:

Hi, I’m pierreg from the gentoo forum :slight_smile:

Did you try by removing the patchs ? One of them may cause your problem. (simply move or remove it/them from files/patchs/)

Hi pierreg,

Just tried compiling 2.5.17 official release with no patches and doesn’t seem to crash anymore. Gonna try cvs version again but with not as many patches.

Thanks

Can compile fvwm-cvs with all patches (which doesn’t agree with rox-filer) or zero patches (with no problems with rox-filer) but instant remove some patches but not all it wont compile.

eg. using patches: 01-MenuTranslucency.patch, 07-FluxboxHandles.patch, 08-RoundedCorners.patch
I’ll get error:

[code]In file included from style.c:36:
fvwm.h:275: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
fvwm.h:276: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
fvwm.h:277: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
fvwm.h:278: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
style.c: In function ‘style_parse_focus_policy_style’:
style.c:1347: warning: large integer implicitly truncated to unsigned type
style.c:1348: warning: large integer implicitly truncated to unsigned type
style.c:1368: warning: large integer implicitly truncated to unsigned type
style.c:1369: warning: large integer implicitly truncated to unsigned type
style.c: In function ‘style_parse_one_style_option’:
style.c:2486: error: 'struct ’ has no member named ‘has_fluxbox_handles’
style.c:2487: error: 'struct ’ has no member named ‘has_fluxbox_handles’
style.c:2488: error: 'struct ’ has no member named ‘has_fluxbox_handles’
style.c:3426: error: 'struct ’ has no member named ‘has_rounded_corners_top’
style.c:3427: error: 'struct ’ has no member named ‘has_rounded_corners_top’
style.c:3428: error: 'struct ’ has no member named ‘has_rounded_corners_top’
style.c:3429: error: 'struct ’ has no member named ‘has_rounded_corners_bottom’
style.c:3430: error: 'struct ’ has no member named ‘has_rounded_corners_bottom’
style.c:3431: error: 'struct ’ has no member named ‘has_rounded_corners_bottom’
style.c:3435: error: 'struct ’ has no member named ‘has_rounded_corners_top’
style.c:3436: error: 'struct ’ has no member named ‘has_rounded_corners_top’
style.c:3437: error: 'struct ’ has no member named ‘has_rounded_corners_top’
style.c:3441: error: 'struct ’ has no member named ‘has_rounded_corners_bottom’
style.c:3442: error: 'struct ’ has no member named ‘has_rounded_corners_bottom’
style.c:3443: error: 'struct ’ has no member named ‘has_rounded_corners_bottom’
style.c:3569: error: 'struct ’ has no member named ‘has_slightly_rounded_corners’
style.c:3570: error: 'struct ’ has no member named ‘has_slightly_rounded_corners’
style.c:3571: error: 'struct ’ has no member named ‘has_slightly_rounded_corners’
style.c: In function ‘check_window_style_change’:
style.c:4436: error: 'struct ’ has no member named ‘has_rounded_corners_top’
style.c:4437: error: 'struct ’ has no member named ‘has_rounded_corners_bottom’
style.c:4438: error: 'struct ’ has no member named ‘has_slightly_rounded_corners’
style.c:4450: error: ‘struct ’ has no member named ‘has_fluxbox_handles’
In file included from events.c:64:
fvwm.h:275: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
fvwm.h:276: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
fvwm.h:277: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
fvwm.h:278: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
make[2]: *** [style.o] Error 1
make[2]: *** Waiting for unfinished jobs…
make[2]: *** [events.o] Error 1
In file included from menus.c:43:
fvwm.h:275: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
fvwm.h:276: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
fvwm.h:277: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
fvwm.h:278: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘attribute’ before ‘:’ token
menus.c: In function ‘pop_menu_up’:
menus.c:4085: warning: pointer targets in passing argument 5 of ‘FScreenGetScrRect’ differ in signedness
menus.c:4085: warning: pointer targets in passing argument 6 of ‘FScreenGetScrRect’ differ in signedness
menus.c: In function ‘get_menu_options’:
menus.c:8147: warning: pointer targets in passing argument 5 of ‘FScreenGetScrRect’ differ in signedness
menus.c:8147: warning: pointer targets in passing argument 6 of ‘FScreenGetScrRect’ differ in signedness
make[2]: *** [menus.o] Error 1
make[2]: Leaving directory /var/tmp/portage/fvwm-9999/work/fvwm/fvwm' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /var/tmp/portage/fvwm-9999/work/fvwm’
make: *** [all] Error 2

!!! ERROR: x11-wm/fvwm-9999 failed.
Call stack:
ebuild.sh, line 1539: Called dyn_compile
ebuild.sh, line 939: Called src_compile
fvwm-9999.ebuild, line 157: Called die

!!! (no error message)
!!! If you need support, post the topmost build error, and the call stack if relevant.

!!! This ebuild is from an overlay: ‘/usr/local/portage’
[/code]Is there something I’m missing? or forget to do?

I get a different error when compiling with only these patchs…
As the author of these patchs said, some individual patchs won’t patch or compile fine alone. We have to apply all the patches in the order he gives.
If I find time for that, I’ll try to correct it.
Keep the original CVS version instead for the moment.

The original issue probably won’t happen with a vanilla version of FVWM (2.5.17 – at the moment, since that has just been released, there’s no need to use CVS).

I suspect there’s a pointer error in one of the patches somewhere. Tut.

– Thomas Adam

Hi,
Can you get a backtrace against a binary with debugging symbols. You should be able to get this by emerging with FEATURES=“nostrip”. I can’t reproduce this with rox so I’m not sure what’s wrong.

[code]gdb fvwm ./core
GNU gdb 6.4
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type “show copying” to see the conditions.
There is absolutely no warranty for GDB. Type “show warranty” for details.
This GDB was configured as “x86_64-pc-linux-gnu”…Using host libthread_db library “/lib/libthread_db.so.1”.

Core was generated by `fvwm’.
Program terminated with signal 11, Segmentation fault.
Cannot access memory at address 0x2b1ea3359000
#0 0x000000000044e590 in __get_corner ()
(gdb) where
#0 0x000000000044e590 in __get_corner ()
Cannot access memory at address 0x7fff07f480f8
[/code]

It might be the same problem from the other thread. I updated it at the time but the ebuild is using the old version.

Try replacing x11-wm/fvwm/files/patchs/08-RoundedCorners.patch with
http://abdn.ac.uk/~u15dm4/fvwm/RoundedCorners.patch and emerging again.

Compiled with new patch seems to fix it, thanks. :smiley: