And here's a backtrace from gdb:

(gdb) run
Starting program: /usr/bin/fstl
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fcc27d49700 (LWP 4164)]
[New Thread 0x7fcc25067700 (LWP 4165)]
[New Thread 0x7fcc1d3df700 (LWP 4166)]
[Thread 0x7fcc1d3df700 (LWP 4166) exited]
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

Thread 1 "fstl" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007fcc31dfe42a in __GI_abort () at abort.c:89
#2  0x00007fcc32713bb5 in __gnu_cxx::__verbose_terminate_handler() ()
   from /lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x00007fcc32711986 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x00007fcc327119d1 in std::terminate() () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x00007fcc32711c14 in __cxa_throw () from
/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007fcc32d03832 in qBadAlloc() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007fcc32d80fba in QListData::detach(int) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007fcc32d2d1ce in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007fcc32ef1b8f in QCoreApplication::arguments() ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fcc33da64df in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#11 0x00007fcc33da7014 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#12 0x00007fcc2ad37d90 in _SmcProcessMessage () from
/lib/x86_64-linux-gnu/libSM.so.6
#13 0x00007fcc2ab272a8 in IceProcessMessages () from
/lib/x86_64-linux-gnu/libICE.so.6
#14 0x00007fcc32f19e51 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fcc32f935ce in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007fcc32f26222 in QSocketNotifier::event(QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007fcc337cbbec in QApplicationPrivate::notify_helper(QObject*,
QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x00007fcc337d3381 in QApplication::notify(QObject*, QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#19 0x00007fcc32eee850 in QCoreApplication::notifyInternal2(QObject*,
QEvent*) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007fcc32f4286d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fcc30360bf7 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fcc30360e60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007fcc30360f0c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x00007fcc32f423bf in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007fcc32eec83a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x00007fcc32ef4edc in QCoreApplication::exec() ()
   from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x000055555555a00b in ?? ()
#28 0x00007fcc31dea2e1 in __libc_start_main (main=0x555555559fe0, argc=1,
    argv=0x7fffffffe0f8, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffe0e8) at
../csu/libc-start.c:291
#29 0x000055555555a0f9 in ?? ()

On Tue, Aug 22, 2017 at 6:54 PM, Eric Cooper <e...@cooper-siegel.org> wrote:
> Here's a core file created when running just "fstl" with no arguments
> (which first printed the following):
>
> terminate called after throwing an instance of 'std::bad_alloc'
>   what():  std::bad_alloc
> Aborted (core dumped)
>
> On Tue, Aug 22, 2017 at 6:09 PM, Jakob Haufe <su...@sur5r.net> wrote:
>> Control: tags -1 + moreinfo
>>
>> Unfortunately, it doesn't crash here. Can you provide me with a coredump or
>> backtrace? Automatic debug packages for fstl 0.9.2-1 exist as well.

Reply via email to