But I'm still having the trouble I've always had. Every time I try to do
something that involves putting up a dialog (Open, Save As, etc), AW dies
with a segfault. Here's the debug stuff:
[larry@curly bin]$ AbiWord
Build ID: curly-larry
Version:
Build Options: JavaScript:Off Debug:On
Compile Date: Dec 3 1998
Compile Time: 23:03:54
DEBUG: EV_Menu: Creating menu for [layout Main, language EnUS]
DEBUG: EV_Toolbar: Creating toolbar for [layout FileEditOps, language EnUS]
DEBUG: EV_Toolbar: Creating toolbar for [layout FormatOps, language EnUS]
DEBUG: Caught combo box change, reformatting!
DEBUG: Caught combo box change, reformatting!
DEBUG: fl_DocListener::populateStrux
DEBUG: fl_DocListener::populateStrux
DEBUG: fl_DocListener::populateStrux
DEBUG: fl_DocListener::populateStrux
DEBUG: BEGIN Formatting document: 0x1929308
DEBUG: BEGIN Formatting block: 0x1929ae8
DEBUG: _verifyCurrentSlice: fl_BlockLayout=0x1929ae8, m_pPrev=0x0
DEBUG: fp_Column::insertBlockSliceAfter - fp_Column=0x192b7c0 slice=0x192b4e8 pAfter=0x0
DEBUG: setColumn: fp_BlockSlice=0x192b4e8, column=0x192b7c0
DEBUG: END Formatting block: 0x1929ae8
DEBUG: END Formatting document: 0x1929308
[...]
DEBUG: Caught combo box change, reformatting!
DEBUG: Caught combo box change, reformatting!
DEBUG: refreshToolbar: ComboBox [Font Size] is enabled and 14
[...]
DEBUG: UnixToolbar_ViewListener::notify [view 0x0192bb38 tb 0x0192bc40][mask 0x00000100]
DEBUG: UnixToolbar_ViewListener::notify [view 0x0192bb38 tb 0x0192bc50][mask 0x00000100]
DEBUG: Scrollbar_ViewListener::notify [view 0x0192bb38 tb 0x0192bc60][mask 0x00000100]
DEBUG: UnixToolbar_ViewListener::notify [view 0x0192bb38 tb 0x0192bc40][mask 0x00000100]
DEBUG: UnixToolbar_ViewListener::notify [view 0x0192bb38 tb 0x0192bc50][mask 0x00000100]
DEBUG: Scrollbar_ViewListener::notify [view 0x0192bb38 tb 0x0192bc60][mask 0x00000100]
DEBUG: invokeMenuMethod: fileSaveAs repeat 1
DEBUG: s_AskForPathname: frame 0x018f5b08, bSaveAs 1, suggest=[]
Gdk-Message:
** ERROR **: sigsegv caught
I'm using MkLinux with gtk+-1.1.3. I've had the same problem with AW
versions 0.1.3, 0.1.6, and now 0.3.0. I don't have a clue where to start
hunting for the problem at this point, but I'd be glad to go looking for it.
Larry