Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QML and Qt Quick
  4. Qt Application Crashes, with coredump Bt not providing enough information
Qt 6.11 is out! See what's new in the release blog

Qt Application Crashes, with coredump Bt not providing enough information

Scheduled Pinned Locked Moved Unsolved QML and Qt Quick
1 Posts 1 Posters 334 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Anita
    wrote on last edited by
    #1

    Hi,

    My Qt application crashes randomly after sometime and the backtrace from core file doesnt show any specific function/operation.

    The bt full is as:
    #0 __libc_do_syscall () at libc-do-syscall.S:49
    No locals.
    #1 0x74453ac4 in __libc_signal_restore_set (set=0x7e9ad5b0) at ../sysdeps/unix/sysv/linux/internal-signals.h:84
    _a2tmp = 2124076464
    _a2 = 2124076464
    _nametmp = 175
    _a3tmp = 0
    _a3 = 0
    _a1 = 0
    _a4tmp = 8
    _a1tmp = 2
    _a4 = 8
    _name = 175
    #2 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:48
    set = {__val = {0, 0, 1964862004, 64381896, 1749816704, 1005024000, 2124076588, 81382584, 2124076568, 1995438336, 79981088, 41, 1749816688,
    64381896, 81382584, 1962560847, 1, 81382584, 81404480, 81382872, 2124076588, 2124076584, 81395972, 1962553719, 81382872, 257, 0, 1995438336,
    2147483648, 81404516, 2124077072, 1950694441}}
    pid = <optimized out>
    tid = <optimized out>
    ret = <optimized out>
    #3 0x744461a6 in __GI_abort () at abort.c:79
    save_stage = 1
    act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, sa_mask = {__val = {64381896, 0, 1995438336, 1995438336, 0, 1554784912,
    2124077152, 1554784792, 0, 1958595216, 4, 1956573335, 2124076952, 0, 28, 1953278036, 1964452700, 7, 81228120, 2124077064, 256, 16843265,
    16843009, 16777217, 0, 0, 1995438336, 0, 13384, 4, 61, 2124077072}}, sa_flags = 1951149423, sa_restorer = 0x1000}
    sigs = {__val = {32, 0 <repeats 31 times>}}
    #4 0x7447bc6e in __libc_message (action=action@entry=do_abort, fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:181
    ap = {__ap = 0x7e9ad84c}
    fd = 2
    list = <optimized out>
    nlist = <optimized out>
    cp = <optimized out>
    written = <optimized out>
    #5 0x74480082 in malloc_printerr (str=<optimized out>) at malloc.c:5336
    No locals.
    #6 0x74481328 in _int_free (av=<optimized out>, p=0x501932c, have_lock=<optimized out>) at malloc.c:4143
    size = 83989328
    fb = <optimized out>
    nextchunk = <optimized out>
    nextsize = <optimized out>
    nextinuse = <optimized out>
    prevsize = <optimized out>
    bck = <optimized out>
    --Type <RET> for more, q to quit, c to continue without paging--
    fwd = <optimized out>
    PRETTY_FUNCTION = "_int_free"
    #7 0x7501f18c in QQmlError::~QQmlError() () from /usr/lib/libQt5Qml.so.5
    No symbol table info available.
    #8 0x74f9c748 in ?? () from /usr/lib/libQt5Qml.so.5
    No symbol table info available.
    Backtrace stopped: previous frame identical to this frame (corrupt stack?).


    The Application is built with 5.15 Arm debug.

    Is there a way in which i can get the point from where the application is crashing?

    1 Reply Last reply
    0

    • Login

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Get Qt Extensions
    • Unsolved