Crashreport Fabariagest 1.0.0


› Forum › Software CodeLinSoft › Fabaria Gest discussion › Question Fedora 22: crashreport Fabariagest 1.0.0 › Crashreport Fabariagest 1.0.0

Autore
Caterpillar
Caterpillar
    Post 37

    Allora, mi son fatto dire come si compilano programmi Qt in modalità debug. Serve la flag -DCMAKE_BUILD_TYPE=Debug
    perciò ho eseguito
    $ cmake -DCMAKE_BUILD_TYPE=Debug -DMAKE_INSTALL_PREFIX=directory -DWANT_QT5=ON -DWANT_QWTQT5=ON
    poi dopo l’installzione ho eseguito
    $ 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...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 19559.
    ASSERT failure in QList::at: "index out of range", file /usr/include/qt5/QtCore/qlist.h, line 510
    [New Thread 0x7fffe0797700 (LWP 19558)]

    Program received signal SIGABRT, Aborted.
    0x00007ffff3dad9c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
    55 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
    (gdb) backtrace
    #0 0x00007ffff3dad9c8 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
    #1 0x00007ffff3daf65a in __GI_abort () at abort.c:89
    #2 0x00007ffff4a6aaf1 in QMessageLogger::fatal(char const*, ...) const (context=..., message=) at global/qlogging.cpp:1575
    #3 0x00007ffff4a6aaf1 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7fffffffd660, msg=msg@entry=0x7ffff4d0ee98 "ASSERT failure in %s: "%s", file %s, line %d")
    at global/qlogging.cpp:777
    #4 0x00007ffff4a65cb1 in qt_assert_x(char const*, char const*, char const*, int) (where=, what=, file=, line=) at global/qglobal.cpp:2978
    #5 0x000000000050cdaf in QList::at(int) const (this=0x7fffffffd6f0, i=1) at /usr/include/qt5/QtCore/qlist.h:510
    #6 0x00000000006bc466 in getSystemInfo() () at /home/user/fabariagest-1.0/fabaria/defines.h:103
    #7 0x00000000006bf011 in main(int, char**) (argc=1, argv=0x7fffffffde18) at /home/user/fabariagest-1.0/fabaria/main.cpp:170
    (gdb)

    Come si può vedere è un backtrace notevolmente più dettagliato dei precedenti

    Crashreport Fabariagest 1.0.0
    #964