From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qmmp: segfaults with projectM-3.1.11 and now FTBFS
Date: Sat, 20 Feb 2021 16:44:36 +0100 [thread overview]
Message-ID: <20210220154436.Z7TKEA6-NECoB7jlttMZpXwd2aSQPnw5wX3lTtVZlnE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28926@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/28926#issuecomment-782701209
Comment:
gdb backtrace after the segfault:
```
(gdb) bt
#0 0x00007fffe80cc197 in PCM::addPCM16 (this=0x0, PCMdata=PCMdata@entry=0x555556a245f8) at PCM.cpp:202
#1 0x00007fffe82285e7 in ProjectMPlugin::onTimeout (this=0x555556a245b0) at ../src/plugins/Visual/projectm/projectmplugin.cpp:99
#2 0x00007ffff6ba27c0 in ?? () from /usr/lib/libQt5Core.so.5
#3 0x00007ffff6ba669a in QTimer::timeout(QTimer::QPrivateSignal) () from /usr/lib/libQt5Core.so.5
#4 0x00007ffff6b9810f in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#5 0x00007ffff780015f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#6 0x00007ffff6b6c1aa in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#7 0x00007ffff6bc2ac3 in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5
#8 0x00007ffff6bc337c in ?? () from /usr/lib/libQt5Core.so.5
#9 0x00007ffff55beccb in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#10 0x00007ffff55bef78 in ?? () from /usr/lib/libglib-2.0.so.0
#11 0x00007ffff55bf02f in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#12 0x00007ffff6bc36ff in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#13 0x00007ffff6b6ab6b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#14 0x00007ffff6b72de0 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#15 0x000055555555b0ce in main (argc=<optimized out>, argv=<optimized out>) at ../src/app/main.cpp:73
```
So it seems `PCM` was not constructed (yet).
next prev parent reply other threads:[~2021-02-20 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 15:27 [ISSUE] " pullmoll
2021-02-20 15:43 ` pullmoll
2021-02-20 15:44 ` pullmoll [this message]
2021-02-20 15:46 ` pullmoll
2021-02-20 16:07 ` pullmoll
2021-02-20 18:40 ` ericonr
2021-02-20 21:28 ` pullmoll
2021-02-20 21:28 ` [ISSUE] [CLOSED] " pullmoll
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210220154436.Z7TKEA6-NECoB7jlttMZpXwd2aSQPnw5wX3lTtVZlnE@z \
--to=pullmoll@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).