Now since VDX can load projects it's time to discover the next crashes ... :-(
a segmentation fault in XmString.c:
#0 0x40361c72 in chunk_alloc (ar_ptr=0x403bc1a0, nb=16) at malloc.c:2616
#1 0x40361b95 in __libc_malloc (bytes=4) at malloc.c:2561
#2 0x401f98a3 in XtMalloc () from /usr/X11R6/lib/libXt.so.6
#3 0x401863c9 in __XmGrowXmString (string=0x83a6d30)
at /home/migdal/mai/compile/lesstif/lesstif/lib/Xm/XmString.c:373
#4 0x401869fc in __XmStringFromASN1 (string=0x8386200 "�\200\006\b\003\001")
at /home/migdal/mai/compile/lesstif/lesstif/lib/Xm/XmString.c:575
#5 0x40187dcd in _XmStringCreate (cs=0x8386200 "�\200\006\b\003\001")
at /home/migdal/mai/compile/lesstif/lesstif/lib/Xm/XmString.c:1203
#6 0x4018d516 in XmStringInitContext (context=0xbfffb358,
string=0x8386200 "�\200\006\b\003\001")
at /home/migdal/mai/compile/lesstif/lesstif/lib/Xm/XmString.c:3927
#7 0x8066451 in LresXmString::cvtXmStringToString (this=0x8388c88,
xmString=0x8386200 "�\200\006\b\003\001", buf=0xbfffb3ac "", size=13)
at Lresource.C:418
[...]
and in __XmGrowXmString (string=0x83a6d30)():
(gdb) p *string
$4 = {components = 0x0, number_of_components = 1}
Not sure what exactly to fix.
The bug seems to be triggered by clicking on 'Generate' in the
RMB menu of an interface (load a project or interface).
I guess either lesstif or vdx corrupts memory somewhere ...
--
Alexander Mai
[EMAIL PROTECTED]
