- Questo topic ha 15 risposte, 3 partecipanti ed è stato aggiornato l'ultima volta Fedora 22: crashreport Fabariagest 1.0.0 da
.
-
Post
-
Vi allego il seguente crashreport (Fedora 22)
[user@localhost fabaria_gest]$ gdb --args fabaria_gest
GNU gdb (GDB) Fedora 7.9-11.fc22
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
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:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from fabaria_gest...Reading symbols from /usr/lib/debug/opt/fabaria_gest/fabaria_gest.debug...(no debugging symbols found)...done.
(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/fabaria_gest/fabaria_gest
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 2343.
[New Thread 0x7fffe17da700 (LWP 2342)]Program received signal SIGSEGV, Segmentation fault.
0x0000000000447bf4 in QBasicAtomicInt::ref() ()
(gdb) backtrace
No stack
Grazie per il feedback.
Provvederemo a risolvere il problema.
Cordialità,
Il team CodeLinSoftIl problema è con le Qt5 sotto fedora 22. Provvedo a risolvere il problema per la 1.1
Per la 1.0 rilascio una patch in modo che la possa includere nei test.
Ecco le QT installate sul mio sistema
qt-4.8.6-30.fc22.x86_64
qt5-qtbase-5.5.0-18.fc22.x86_64
qt5-qtbase-common-5.5.0-18.fc22.noarch
qt5-qtbase-gui-5.5.0-18.fc22.x86_64
qt5-qtdeclarative-5.5.0-3.fc22.x86_64
qt5-qtgraphicaleffects-5.5.0-2.fc22.x86_64
qt5-qtlocation-5.5.0-3.fc22.x86_64
qt5-qtmultimedia-5.5.0-3.fc22.x86_64
qt5-qtquickcontrols-5.5.0-3.fc22.x86_64
qt5-qtscript-5.5.0-3.fc22.x86_64
qt5-qtsensors-5.5.0-3.fc22.x86_64
qt5-qtsvg-5.5.0-3.fc22.x86_64
qt5-qttools-5.5.0-4.fc22.x86_64
qt5-qttools-common-5.5.0-4.fc22.noarch
qt5-qttools-libs-designer-5.5.0-4.fc22.x86_64
qt5-qtwebkit-5.5.0-4.fc22.x86_64
qt5-qtx11extras-5.5.0-2.fc22.x86_64
qt5-qtxmlpatterns-5.5.0-3.fc22.x86_64
qt-at-spi-0.3.1-7.fc22.x86_64
qt-common-4.8.6-30.fc22.noarch
qt-debuginfo-4.8.6-30.fc22.x86_64
qt-gstreamer-1.2.0-3.fc22.x86_64
qt-mobility-common-1.2.2-0.17.20140317git169da60c.fc22.x86_64
qt-mobility-debuginfo-1.2.2-0.17.20140317git169da60c.fc22.x86_64
qt-mobility-location-1.2.2-0.17.20140317git169da60c.fc22.x86_64
qt-mobility-sensors-1.2.2-0.17.20140317git169da60c.fc22.x86_64
qt-mysql-4.8.6-30.fc22.x86_64
qtscriptbindings-0.2.0-8.fc22.x86_64
qt-settings-22-14.fc22.noarch
qtsoap-2.7-9.fc22.x86_64
qtsoap-debuginfo-2.7-9.fc22.x86_64
qtwebkit-2.3.4-6.fc22.x86_64
qtwebkit-debuginfo-2.3.4-6.fc22.x86_64
qt-x11-4.8.6-30.fc22.x86_64
Non vedo però Qt MySQL x le qt5 e qt4.
Inviato dal mio M-PPxG510 utilizzando Tapatalk
Per QT4
qt-mysql-4.8.6-30.fc22.x86_64
presente nella lista. Per la versione QT5 c’è il pacchetto
qt5-qtbase-mysql
che ho installato ora e che non era stato installato a causa probabilmente della mancanza del riferimento alla dipendenza nel file .spec dell’RPM.
L’aver installato tale pacchetto non cambia la situazioneGrazie mille. Io come te lavoro sotto Fedora 22 e questo problema si è presentato qualche giorno fa dove rilasciati gli aggiornamenti e tutto ha funzionato come prima
Inviato dal mio M-PPxG510 utilizzando Tapatalk
Scarica il sorgente dal sito e prova. Può darsi che ci sia un errore nel rpm
Inviato dal mio M-PPxG510 utilizzando Tapatalk
Eccoci qui. Con il programma compilato da sorgente sono riuscito ad avere un backtrace migliore
[user@localhost fabaria_gest]$ gdb fabaria_gest
GNU gdb (GDB) Fedora 7.9.1-19.fc22
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
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:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from fabaria_gest...(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/fabaria_gest/fabaria_gest
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".Program received signal SIGSEGV, Segmentation fault.
QList (this=0x7ffff3636438
121 inline QList() : d(&QListData::shared_null) { d->ref.ref(); }
(gdb) backtrace
#0 0x00007ffff2affc74 in _GLOBAL__sub_I_qprinterinfo.cpp(void) (this=0x7ffff3636438
Python Exceptionmaximum recursion depth exceeded while getting the str of an object:
#1 0x00007ffff2affc74 in _GLOBAL__sub_I_qprinterinfo.cpp(void) (name=..., this=0x7ffff3636420
#2 0x00007ffff2affc74 in _GLOBAL__sub_I_qprinterinfo.cpp(void) (__initialize_p=1, __priority=65535) at painting/qprinterinfo.cpp:35
#3 0x00007ffff2affc74 in _GLOBAL__sub_I_qprinterinfo.cpp(void) () at painting/qprinterinfo.cpp:163
#4 0x00007ffff7deb63a in call_init (l=, argc=argc@entry=1, argv=argv@entry=0x7fffffffde18, env=env@entry=0x7fffffffde28) at dl-init.c:72
#5 0x00007ffff7deb74b in _dl_init (env=0x7fffffffde28, argv=0x7fffffffde18, argc=1, l=) at dl-init.c:30
#6 0x00007ffff7deb74b in _dl_init (main_map=0x7ffff7ffe148, argc=1, argv=0x7fffffffde18, env=0x7fffffffde28) at dl-init.c:120
#7 0x00007ffff7ddccba in _dl_start_user () at /lib64/ld-linux-x86-64.so.2
#8 0x0000000000000001 in ()
#9 0x00007fffffffe17f in ()
#10 0x0000000000000000 in ()
(gdb)
Noto che è un problema del pacchetto rpm. Il sorgente funziona
Inviato dal mio M-PPxG510 utilizzando Tapatalk
=”Angelo Scarnà” post=290]Noto che è un problema del pacchetto rpm. Il sorgente funziona
No, non funziona altrimenti non avrei tirato fuori un nuovo backtrace 🙂
Il backtrace che hai postato mi fa vedere /opt/fabaria e non il file compilato
Inviato dal mio M-PPxG510 utilizzando Tapatalk
Ho disinstallato gli RPM di FabariaGest e reinstallato la versione da codice sorgente. Ecco il backtrace
[caterpillar@localhost fabaria_gest]$ gdb fabaria_gest
GNU gdb (GDB) Fedora 7.9.1-19.fc22
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
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:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from fabaria_gest...(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/fabaria_gest/fabaria_gest
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 7246.
[New Thread 0x7fffe0798700 (LWP 7244)]Program received signal SIGSEGV, Segmentation fault.
0x00000000004f568c in QBasicAtomicInteger::load() const ()
(gdb) backtrace
#0 0x00000000004f568c in QBasicAtomicInteger::load() const ()
#1 0x0000000000502a92 in QtPrivate::RefCount::ref() ()
#2 0x0000000000502e37 in QString::QString(QString const&) ()
#3 0x00000000006b9709 in _ZL13getSystemInfov ()
#4 0x00000000006bc29f in main ()
(gdb)
#0 0x00Grazie adesso so dove risiede il problema
Inviato dal mio M-PPxG510 utilizzando Tapatalk
Ciao Caterpillar,
allora ho installato come te il file rpm di fedora nella mia distribuzione. Lancia da terminale
dnf updatee vedi gli aggiornamenti.
Altra cosa questo è il mio bug report sotto fedora 22. Io utilizzo proprio fedora come ambiente di sviluppo, per questo ho fatto tutte le verifiche del caso. QAtomicInt è una classe delle qt che va a leggere la memoria utilizzata dal software o da qualunque programma che usa le Qt. In parole povere al posto di usare malloc o realloc in c++ si usa QAtomicInt dove ref() e deref() fanno lo stesso lavoro di malloc.
gdb --args ./fabaria_gest
GNU gdb (GDB) Fedora 7.9.1-19.fc22
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
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:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./fabaria_gest...Reading symbols from /usr/lib/debug/opt/fabaria_gest/fabaria_gest.debug...(no debugging symbols found)...done.
(no debugging symbols found)...done.
(gdb) run
Starting program: /opt/fabaria_gest/fabaria_gest
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 6754.
Detaching after fork from child process 6772.
Detaching after fork from child process 6773.
QSqlDatabasePrivate::removeDatabase: connection 'qt_sql_default_connection' is still in use, all queries will cease to work.
QSqlDatabasePrivate::addDatabase: duplicate connection name 'qt_sql_default_connection', old connection removed.
Detaching after fork from child process 6777.
[Inferior 1 (process 6749) exited normally]
Missing separate debuginfos, use: dnf debuginfo-install attica-0.4.2-4.fc22.x86_64 dbusmenu-qt-0.9.3-0.10.20150604.fc22.x86_64 gamin-0.1.10-17.fc22.x86_64 herqq-1.0.0-8.fc22.x86_64 ibus-qt-1.3.3-5.fc22.x86_64 ilmbase-2.2.0-1.fc22.x86_64 kdelibs-4.14.12-1.fc22.x86_64 kde-platform-plugin-4.11.22-2.fc22.x86_64 kde-runtime-libs-15.08.1-2.fc22.x86_64 kde-style-breeze-5.4.1-1.fc22.x86_64 libacl-2.2.52-7.fc22.x86_64 libXft-2.3.2-2.fc22.x86_64 libxml2-2.9.2-4.fc22.x86_64 libXpm-3.5.11-3.fc22.x86_64 libXtst-1.2.2-4.fc22.x86_64 OpenEXR-libs-2.2.0-1.fc22.x86_64 qca-2.1.0-14.fc22.x86_64 soprano-2.9.4-5.fc22.x86_64 strigi-libs-0.7.8-7.fc22.x86_64
(gdb) run
Starting program: /opt/fabaria_gest/fabaria_gest
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 6806.
Detaching after fork from child process 6825.
Detaching after fork from child process 6826.
[New Thread 0x7fffd2214700 (LWP 6831)]
[Thread 0x7fffd2214700 (LWP 6831) exited]
[Thread 0x7ffff7fa38c0 (LWP 6804) exited]
[Inferior 1 (process 6804) exited normally]
Missing separate debuginfos, use: dnf debuginfo-install appmenu-qt-0.2.6-6.fc22.x86_64 nss-mdns-0.10-15.fc22.x86_64 sni-qt-0.2.6-4.fc22.x86_64
(gdb) run
Starting program: /opt/fabaria_gest/fabaria_gest
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 6835.
Detaching after fork from child process 6854.
Detaching after fork from child process 6855.
[New Thread 0x7fffd241e700 (LWP 6860)]
[Thread 0x7fffd241e700 (LWP 6860) exited]
[Inferior 1 (process 6833) exited normally]
(gdb) backtrace
No stack.
(gdb)Prova e fammi sapere.
- Il topic ‘ Question Fedora 22: crashreport Fabariagest 1.0.0’ è chiuso a nuove risposte.