CAD-3.28.2.2 crashes

Use this forum for all posts and questions about the free QCAD Community Edition version 3

Moderator: andrew

Post Reply
sagitter
Active Member
Posts: 25
Joined: Mon Dec 05, 2016 12:31 pm

CAD-3.28.2.2 crashes

Post by sagitter » Tue Nov 07, 2023 8:35 pm

QCAD-3.28.2.2 is crashing in Fedora 38+ with this error:

Code: Select all

terminate called after throwing an instance of 'Tools::IllegalArgumentException'

Thread 1 "qcad-bin" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
Downloading source file /usr/src/debug/glibc-2.37-13.fc38.x86_64/nptl/pthread_kill.c
44            return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0;        


If you can, install QCAD from Fedora 38 repository, run it and try to add a simple line; qcad will crash in some seconds.

CVH
Premier Member
Posts: 3480
Joined: Wed Sep 27, 2017 4:17 pm

Re: CAD-3.28.2.2 crashes

Post by CVH » Wed Nov 08, 2023 6:24 am

Hi,

First, QCAD-3.28.2.2 is a snapshot release, stable releases end in point zero.
Second, what with the official release? If that runs fine then I think you need to contact the repository manager.
(But you or someone else already did that on 2023-11-07 17:57 UTC, probably it is you that is the assignee)

Further, I wonder how you sourced the snapshot.
On the download page, at the bottom, section: QCAD Community Edition Source Code
  • QCAD Source: v3.28.2.0.zip

I can only refer to Andrew's reply what should sound familiar to you:
https://www.qcad.org/rsforum/viewtopic. ... 820#p27820

I would stick to official releases. :wink:

Regards,
CVH

sagitter
Active Member
Posts: 25
Joined: Mon Dec 05, 2016 12:31 pm

Re: CAD-3.28.2.2 crashes

Post by sagitter » Wed Nov 08, 2023 9:39 pm

Hi CVH

First, where QCAD-3.28.2.2 is spread as snapshot?
Here? No.
Here? No.

The date of release 3.28.2.2 is the same of the 3.28.2 one, so what is the snapshot and what is the stable release?

Second, the repository manager is me and i saying that your snapshot is crashing for some reason, does anyone interest this?

User avatar
andrew
Site Admin
Posts: 9063
Joined: Fri Mar 30, 2007 6:07 am

Re: CAD-3.28.2.2 crashes

Post by andrew » Wed Nov 08, 2023 10:07 pm

sagitter: Please use only x.x.x.0 tags for releases as these have been tested on all major platforms (Windows, macOS, Linux) with Qt 5 (and Qt 6 where applicable).

The QCAD ecosystem is much larger than its open source core and we use the x.x.x.[1-9] tags across dozens of repositories for releases that often target a single platform / customer / Qt version.

sagitter
Active Member
Posts: 25
Joined: Mon Dec 05, 2016 12:31 pm

Re: CAD-3.28.2.2 crashes

Post by sagitter » Wed Nov 08, 2023 10:12 pm

Okay Andrew. Thank you.

sagitter
Active Member
Posts: 25
Joined: Mon Dec 05, 2016 12:31 pm

Re: CAD-3.28.2.2 crashes

Post by sagitter » Wed Nov 08, 2023 11:02 pm

QCAD-3.28.2.0 is crashing at the same way of 3.28.2.2
The 3.27.9.0 works fine.

Do you want to try it?
https://koji.fedoraproject.org/koji/tas ... =108767461

CVH
Premier Member
Posts: 3480
Joined: Wed Sep 27, 2017 4:17 pm

Re: CAD-3.28.2.2 crashes

Post by CVH » Thu Nov 09, 2023 9:32 am

sagitter wrote:
Wed Nov 08, 2023 9:39 pm
First, where QCAD-3.28.2.2 is spread as snapshot?
As far as I know official snapshots are: A) No longer announced; B) Available for Pro licence users in their private download area.

These snapshots never have failed big time and in most cases newer code or patches will live on in further releases.
Or as in the case 3.27.9 >> 3.28.0 the Library Browser was retired for CE and replaced by one for the Pro version.
There is no certainty that all this is bug free but major bug's are handled as soon as they are detected/reported.
e.g:
-> https://www.qcad.org/rsforum/viewtopic.php?f=33&t=9588
The extreme lag in 3.27.7 originated from chopping 480 arcs in 158 line segments each resulting in a hatch boundary defined by 76324 segments.
-> https://www.qcad.org/rsforum/viewtopic. ... 374#p42574
The crash was reproducible and that should be fixed for the next release/snapshot.
-> ...

And then there are still non-critical practical bug's unrelated to newer releases, filed several, some included a fix.
sagitter wrote:
Wed Nov 08, 2023 9:39 pm
so what is the snapshot and what is the stable release?
As in my reply and confirmed by Andrew these end in point zero.
sagitter wrote:
Wed Nov 08, 2023 11:02 pm
QCAD-3.28.2.0 is crashing at the same way of 3.28.2.2
The 3.27.9.0 works fine.
Noop, I can not agree, many users updated to 3.28.x and many even use the 3.28.2.2 snapshot.
I even installed QCAD/CAM 3.28.2 trial aside for the crash mentioned above: https://www.qcad.org/rsforum/viewtopic. ... 374#p42574
Works just fine on my ancient 32 bit Win7 PC but it remains a limited QCAD/CAM trial.

And then I refer to official releases or snapshots for a specific OS, a specific CPU, with dedicated Qt and/or other specifics.
Under All Downloads there are 21 choices listed: https://www.ribbonsoft.com/en/download

Have you even tried to install the official release on your system before saying that it fails big time?
This should be as easy as downloading the correct Pro trial version for your system and remove some files.
See: https://www.qcad.org/rsforum/viewtopic.php?f=76&t=4668
Did that for this topic, takes about 8min and it works just fine ... Limited as it is only the CE version.
Maybe that is the best way to include it in the repository ... ?

IMHO the compilation from sources failed.
Shot in the dark: If QCAD does startup as you say but fails for executing a command ... What if you startup in debug mode.
Would that tell more than: "received signal SIGABRT, Aborted."?

As last I can only refer to a reply of Andrew, way back in 2019:
https://www.qcad.org/rsforum/viewtopic. ... 477#p25477

Regards,
CVH

sagitter
Active Member
Posts: 25
Joined: Mon Dec 05, 2016 12:31 pm

Re: CAD-3.28.2.2 crashes

Post by sagitter » Thu Nov 09, 2023 7:15 pm

Have you even tried to install the official release on your system before saying that it fails big time?
Done right now, it's working.
Maybe that is the best way to include it in the repository ... ?
No; i can't include precompiled libraries and software in Fedora.
IMHO the compilation from sources failed.
Me too, at this point. Searching in my build log i found these lines:

Code: Select all

g++ -c -pipe -O2 -O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -DQT_UITOOLS_LIB -I/usr/include/qt5/QtUiTools -I/usr/include/qt5 -DQT_WIDGETS_LIB -I/usr/include/qt5/QtWidgets -DQT_GUI_LIB -I/usr/include/qt5/QtGui -DQT_CORE_LIB -I/usr/include/qt5/QtCore -Wall -Wextra -D_REENTRANT -fPIC -DQT_DISABLE_DEPRECATED_BEFORE=0x000000 -DQCAD_DLL -DQCADSPATIALINDEX_LIBRARY -DQT_NO_DEBUG -DQT_PLUGIN -DQT_PRINTSUPPORT_LIB -DQT_SVG_LIB -DQT_OPENGL_LIB -DQT_HELP_LIB -DQT_UITOOLS_LIB -DQT_DESIGNER_LIB -DQT_UIPLUGIN_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_SQL_LIB -DQT_XMLPATTERNS_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SCRIPT_LIB -DQT_SCRIPTTOOLS_LIB -DQT_CORE_LIB -DQDESIGNER_EXPORT_WIDGETS -I. -I../core -I../core/math -I../grid -I../snap -I../gui -I../entity -I../operations -I../scripting -I../stemmer -I../scripting/ecmaapi -I../scripting/ecmaapi/generated -I../scripting/ecmaapi/adapters -I../io/dxf -I. -I../3rdparty -I/builddir/build/BUILD/qcad-3.28.2.2/src/zip -I../3rdparty/legacy/spatialindexnavel -I/usr/include/qt5 -I/usr/include/qt5/QtPrintSupport -I/usr/include/qt5/QtSvg -I/usr/include/qt5/QtOpenGL -I/usr/include/qt5/QtHelp -I/usr/include/qt5/QtUiTools -I/usr/include/qt5/QtDesigner -I/usr/include/qt5/QtUiPlugin -I/usr/include/qt5/QtWidgets -I/usr/include/qt5/QtGui -I/usr/include/qt5/QtSql -I/usr/include/qt5/QtXmlPatterns -I/usr/include/qt5/QtNetwork -I/usr/include/qt5/QtXml -I/usr/include/qt5/QtScript -I/usr/include/qt5/QtScriptTools -I/usr/include/qt5/QtCore -Irelease -I/usr/lib64/qt5/mkspecs/linux-g++ -o release/RSpatialIndexNavel.o RSpatialIndexNavel.cpp
make[3]: Leaving directory '/builddir/build/BUILD/qcad-3.28.2.2/src/spatialindex'
RSpatialIndexNavel.cpp: In member function 'virtual void RSpatialIndexNavel::bulkLoad(const QList<int>&, const QList<QList<RBox> >&)':
RSpatialIndexNavel.cpp:170:43: warning: catching polymorphic type 'class Tools::IllegalArgumentException' by value [-Wcatch-value=]
  170 |     catch(Tools::IllegalArgumentException e) {
      |                                           ^
and i suspect that unbundling spatialindex-1.9.1 in your source code archive (in favour of the spatialindex-1.9.3 from Fedora repositories) is a bad idea. I recompiled QCAD-3.28.2.0 with bundled spatialindex-1.9.1, it's correctly executed now.

IShot in the dark: If QCAD does startup as you say but fails for executing a command ... What if you startup in debug mode.
Would that tell more than: "received signal SIGABRT, Aborted."?

Code: Select all

atu@hatu:~/rpm/box127$ /usr/bin/gdb /usr/lib64/qcad/qcad-bin
GNU gdb (Fedora Linux) 13.2-7.fc39
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib64/qcad/qcad-bin...

This GDB supports auto-downloading debuginfo from the following URLs:
  <https://debuginfod.fedoraproject.org/>
Enable debuginfod for this session? (y or [n]) n
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
Reading symbols from .gnu_debugdata for /usr/lib64/qcad/qcad-bin...
(No debugging symbols found in .gnu_debugdata for /usr/lib64/qcad/qcad-bin)
Missing separate debuginfos, use: dnf debuginfo-install qcad-3.28.2.2-1.fc40.x86_64
(gdb) run
Starting program: /usr/lib64/qcad/qcad-bin 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffefa356c0 (LWP 162280)]
[New Thread 0x7fffef2346c0 (LWP 162281)]
[New Thread 0x7fffecb436c0 (LWP 162282)]
[New Thread 0x7fffe59ff6c0 (LWP 162283)]
[New Thread 0x7fffd89ff6c0 (LWP 162284)]
[New Thread 0x7fff4bfff6c0 (LWP 162285)]
[New Thread 0x7fff4b7fe6c0 (LWP 162286)]
[New Thread 0x7fff4affd6c0 (LWP 162287)]
[New Thread 0x7fff4a7fc6c0 (LWP 162288)]
Warning:  Could not find any platform plugin

Thread 1 "qcad-bin" received signal SIGSEGV, Segmentation fault.
0x00007ffff36a0b50 in typeinfo name for SpatialIndex::IStatistics () from /usr/lib64/qcad/libspatialindexnavel.so
(gdb) bt
#0  0x00007ffff36a0b50 in typeinfo name for SpatialIndex::IStatistics () at /usr/lib64/qcad/libspatialindexnavel.so
#1  0x00007ffff6470202 in RSpatialIndexNavel::uninit() () at /usr/lib64/qcad/libqcadspatialindex.so
#2  0x00007ffff6470235 in RSpatialIndexNavel::clear() () at /usr/lib64/qcad/libqcadspatialindex.so
#3  0x00007ffff6004750 in RDocument::clearSpatialIndices() () at /usr/lib64/qcad/libqcadcore.so
#4  0x00007ffff600a833 in RDocument::clear(bool) () at /usr/lib64/qcad/libqcadcore.so
#5  0x00007ffff601df27 in RDocumentInterface::clear(bool) () at /usr/lib64/qcad/libqcadcore.so
#6  0x00007ffff602153d in RDocumentInterface::importFile(QString const&, QString const&, bool, QMap<QString, QVariant> const&) ()
    at /usr/lib64/qcad/libqcadcore.so
#7  0x00007ffff6e09b8d in REcmaDocumentInterface::importFile(QScriptContext*, QScriptEngine*) () at /usr/lib64/qcad/libqcadecmaapi.so
#8  0x00007ffff3fd3c9c in QScript::FunctionWrapper::proxyCall(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) ()
    at /lib64/libQt5Script.so.5
#9  0x00007ffff3efdf40 in QTJSC::NativeFuncWrapper::operator()(QTJSC::ExecState*, QTJSC::JSObject*, QTJSC::JSValue, QTJSC::ArgList const&) const ()
    at /lib64/libQt5Script.so.5
#10 0x00007ffff3ed9d37 in cti_op_call_NotJSFunction () at /lib64/libQt5Script.so.5
#11 0x00007fff4c36f862 in  ()
#12 0x00007fff48ab7f78 in  ()
#13 0x00007fffd25c5680 in  ()
#14 0x00007fff00000021 in  ()
#15 0x96bc371f00000003 in  ()
#16 0x00007fffe4ed8f40 in  ()
#17 0x00007fff00000004 in  ()
#18 0x00007fffd088f5b0 in  ()
#19 0x00007fffd07b8900 in  ()
#20 0x00007fffffffb800 in  ()
#21 0x00007fff4c268000 in  ()
#22 0x00007fffe4703750 in  ()
#23 0x00007fffe4300d30 in  ()
#24 0x00007fffe4709a88 in  ()
#25 0x00007ffff4053248 in  () at /lib64/libQt5Script.so.5
#26 0x00007fffe4708800 in  ()
#27 0x00007fffe4300b58 in  ()
#28 0x00007fffe4703750 in  ()
#29 0x00007ffff4053248 in  () at /lib64/libQt5Script.so.5
#30 0x00007fffe4300228 in  ()
#31 0x00007fffe4703738 in  ()
#32 0x00007fffffffb880 in  ()
#33 0x00007ffff3e90385 in QTJSC::Interpreter::execute(QTJSC::FunctionExecutable*, QTJSC::ExecState*, QTJSC::JSFunction*, QTJSC::JSObject*, QTJSC::ArgList const&, QTJSC::ScopeChainNode*, QTJSC::JSValue*) () at /lib64/libQt5Script.so.5
(gdb) 

CVH
Premier Member
Posts: 3480
Joined: Wed Sep 27, 2017 4:17 pm

Re: CAD-3.28.2.2 crashes

Post by CVH » Thu Nov 09, 2023 10:32 pm

sagitter wrote:
Thu Nov 09, 2023 7:15 pm
and i suspect that unbundling spatialindex-1.9.1 in your source code archive (in favour of the spatialindex-1.9.3 from Fedora repositories) is a bad idea. I recompiled QCAD-3.28.2.0 with bundled spatialindex-1.9.1, it's correctly executed now.
Fine for you but remember that it is not my source code archive.
As simple QCAD user I was just replying to the title 'CAD-3.28.2.2 crashes' what is untrue.
That is, official releases do not as you just agreed on.

Dug a little deeper and it seems that all your 25 posts are related to Fedora.
You got your answer about what are stable releases back in 2020:
andrew wrote:
Thu Apr 16, 2020 10:39 am
x.x.x.0 are stable releases
And another quote:
andrew wrote:
Thu Nov 14, 2019 9:14 am
We are unable to provide support for compiling / using QCAD CE, but feel free to discuss QCAD CE issues at the dedicated forum at:
https://qcad.org/rsforum/viewforum.php?f=76
And then I think Andrew refers to issues when using QCAD CE.

With this I think that everything is said.

Regards,
CVH

Post Reply

Return to “QCAD Community Edition”