BricsCAD V22 - Crash probably on lisp engine

Massimo Del Fedele

Hello,
on NEW (almost empty) drawing, no crash.
On a drawing containing some entities, launching APPLOAD or BLADE crashes.
Here the gdb backtrace for APPLOAD :

Thread 1 "bricscad" received signal SIGSEGV, Segmentation fault.
0x00007fff46439d89 in getLoadedLispFiles () from /opt/bricsys/bricscad/v22/liblispex.so
(gdb) bt
#0 0x00007fff46439d89 in getLoadedLispFiles () at /opt/bricsys/bricscad/v22/liblispex.so
#1 0x00007ffff0a22fda in wxg::CApploadFilesMngr::initLoadedLspFiles() () at /opt/bricsys/bricscad/v22/libwxgui.so
#2 0x00007ffff0a26a2e in wxg::CApploadFilesMngr::init(wxString const&) () at /opt/bricsys/bricscad/v22/libwxgui.so
#3 0x00007ffff0a26a97 in wxg::DlgLoadApp::launchDlg(wxWindow*) () at /opt/bricsys/bricscad/v22/libwxgui.so
#4 0x00007ffff7cabbeb in cmd_appload(ca::CaDoc*) () at /opt/bricsys/bricscad/v22/libcommands.so
#5 0x00007fffee47898d in ca::InternalCommand::execute(OdEdCommandContext*) ()
at /opt/bricsys/bricscad/v22/libcadapp.so
#6 0x00007ffff5954240 in OdEdCommandStackImpl::executeCommand(OdEdCommand*, OdEdCommandContext*) ()
at /opt/bricsys/bricscad/v22/libTD_Root.so
#7 0x00007fffee221171 in ca::CommandProcessor::execCommand(OdEdCommand*, bool&, bool) ()
at /opt/bricsys/bricscad/v22/libcadapp.so
#8 0x00007fffee225d91 in ca::CommandProcessor::execStr(OdString&, bool, OdEdCommand*, bool, bool, ca::Alias*) ()
at /opt/bricsys/bricscad/v22/libcadapp.so
#9 0x00007fffee226f56 in ca::CommandProcessor::processString(OdString const&, bool) ()
at /opt/bricsys/bricscad/v22/libcadapp.so
#10 0x00007fffee228c97 in ca::CommandProcessor::processNextCmdItem(int) () at /opt/bricsys/bricscad/v22/libcadapp.so
#11 0x00007fffee228ed3 in ca::CommandProcessor::processIdle() () at /opt/bricsys/bricscad/v22/libcadapp.so
#12 0x00007fffee22bcd8 in ca::CommandProcessor::main() () at /opt/bricsys/bricscad/v22/libcadapp.so
#13 0x00007fffee229038 in ca::CommandProcessor::start() () at /opt/bricsys/bricscad/v22/libcadapp.so
#14 0x00007fffee2290f5 in ca::CommandProcessor::mainWorkFlowProc(void*) () at /opt/bricsys/bricscad/v22/libcadapp.so
#15 0x00007fffdc40778b in () at /opt/bricsys/bricscad/v22/libpth.so.20
#16 0x00007fffe98d0180 in __start_context () at ../sysdeps/unix/sysv/linux/x86_64/__start_context.S:90
#17 0x0000000000000000 in ()

And the backtrace for BLADE :

Thread 1 "bricscad" received signal SIGSEGV, Segmentation fault.
0x00007fff4613efd9 in olmakesymbolcase.constprop () from /opt/bricsys/bricscad/v22/liblispex.so
(gdb) bt
#0 0x00007fff4613efd9 in olmakesymbolcase.constprop () at /opt/bricsys/bricscad/v22/liblispex.so
#1 0x00007fff4623ef62 in CVLIdeDebugConnector::CVLIdeDebugConnector(CVLIdeDebugHost&) () at /opt/bricsys/bricscad/v22/liblispex.so
#2 0x00007fff461da346 in CVLIdeDebugHost::CVLIdeDebugHost() () at /opt/bricsys/bricscad/v22/liblispex.so
#3 0x00007fff4615e197 in CVLIdeFrame::CVLIdeFrame(CVLIdeHolder*) () at /opt/bricsys/bricscad/v22/liblispex.so
#4 0x00007fff4615fb0d in CVLIdeHolder::createOrShow(bool, bool) () at /opt/bricsys/bricscad/v22/liblispex.so
#5 0x00007ffff7cabed5 in cmd_vlide() () at /opt/bricsys/bricscad/v22/libcommands.so
#6 0x00007fffee4782e8 in ca::InternalCommand::execute(OdEdCommandContext*) () at /opt/bricsys/bricscad/v22/libcadapp.so
#7 0x00007ffff5954240 in OdEdCommandStackImpl::executeCommand(OdEdCommand*, OdEdCommandContext*) () at /opt/bricsys/bricscad/v22/libTD_Root.so
#8 0x00007fffee221171 in ca::CommandProcessor::execCommand(OdEdCommand*, bool&, bool) () at /opt/bricsys/bricscad/v22/libcadapp.so
#9 0x00007fffee225d91 in ca::CommandProcessor::execStr(OdString&, bool, OdEdCommand*, bool, bool, ca::Alias*) ()
at /opt/bricsys/bricscad/v22/libcadapp.so
#10 0x00007fffee226f56 in ca::CommandProcessor::processString(OdString const&, bool) () at /opt/bricsys/bricscad/v22/libcadapp.so
#11 0x00007fffee228c97 in ca::CommandProcessor::processNextCmdItem(int) () at /opt/bricsys/bricscad/v22/libcadapp.so
#12 0x00007fffee228ed3 in ca::CommandProcessor::processIdle() () at /opt/bricsys/bricscad/v22/libcadapp.so
#13 0x00007fffee22bcd8 in ca::CommandProcessor::main() () at /opt/bricsys/bricscad/v22/libcadapp.so
#14 0x00007fffee229038 in ca::CommandProcessor::start() () at /opt/bricsys/bricscad/v22/libcadapp.so
#15 0x00007fffee2290f5 in ca::CommandProcessor::mainWorkFlowProc(void*) () at /opt/bricsys/bricscad/v22/libcadapp.so
#16 0x00007fffdc40778b in () at /opt/bricsys/bricscad/v22/libpth.so.20
#17 0x00007fffe98d0180 in __start_context () at ../sysdeps/unix/sysv/linux/x86_64/__start_context.S:90
#18 0x0000000000000000 in ()

As you can see, the crash is in both cases in "liblispex" library, but at different locations.
If I start with an EMPTY drawing I've got NO CRASH. I can add entities, and still no crash.
But if I save the drawing and re-open it, the crash is there again.

Now, the weird : If I open the drawing, issue a (load "somenonexistinglisp") command
then the APPLOAD and BLADE commands works perfectly.
I think there's some missing module load which is corrected by the (load "somenonexistinglisp"), but not sure.

Ciao

Massimo

p.s.: Ubuntu 22.04 LTS, 64 BIT

Torsten Moses

Dear Massimo,
are you using the latest BricsCAD V22 version on your Ubuntu ?
Will try to reproduce in my Mint 19 VM, as the problem you described sounds really weired ...
many greetings & more to come

P.S. maybe you can add a support request, so our support team can also try to reproduce on their Linux machines ?

Massimo Del Fedele

Torsten Moses said:

Dear Massimo,
are you using the latest BricsCAD V22 version on your Ubuntu ?
Will try to reproduce in my Mint 19 VM, as the problem you described sounds really weired ...
many greetings & more to come

P.S. maybe you can add a support request, so our support team can also try to reproduce on their Linux machines ?

Yes, using V22, trial mode. I'd like to test id in depth before migrating from autocad... by now I'm using an old AutoCAD 2005 on wine, the latest that runs reliably in Linux.
By now I'm impressed with Bricscad, besides some caveats and some (many ?) crashes.

I'll be glad to help, up the evaluation time expires.
I could test it on anorher linux machine, if it can be useful, but all of my machines are updated to ubuntu 22.04, and (now) I've got no time to prepare e virtual machine with a different version.