On Sat, Jul 20, 2002 at 01:17:49PM +0200, Uwe Pross wrote: > Hi there, > > Yesterday I realized a reproducable crash of fvwm 2.5.2 and X when > using a menu which is created by fvwm-menu-directory: > > DestroyFunc FuncFvwmMenuDirectory > AddToFunc FuncFvwmMenuDirectory I PipeRead "fvwm-menu-directory \ > --icon-dir=mini_filesystems.folder.xpm \ > --icon-file=mini_filesystems.File.xpm \ > --icon-app=mini_filesystems.exec.xpm $1 --exec-file=jed --dir=$0" > > DestroyMenu myFileBrowserMenu > AddToMenu myFileBrowserMenu "File Browser" Title > + MissingSubmenuFunction FuncFvwmMenuDirectory > + "Files" Popup $[HOME] > + "Files (All)" Popup $[HOME] "--all" > > fvwm does not crash immediately. When using the menu above repeatedly > and using other menus between them it crashes. I could reproduce this > behavior several times. > > I used gdb to see where the crash comes from. The output of gdb which > contains the stack trace after the crash is attached to this mail.
I think I've already fixed this one in poost-2.5.2 CVS. Could you please try a current snapshot? Bye Dominik ^_^ ^_^ -- Dominik Vogt, [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] -- 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]
