From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] swell-foop crashes
Date: Sun, 13 Oct 2019 20:43:58 +0200 [thread overview]
Message-ID: <20191013184358.5AZQcIdbHOh2bgtQ35-dY2fMStou-GWt7DE7fNJq8Aw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14477@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3197 bytes --]
Closed issue by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/14477
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
*Void 5.2.14_1 x86_64 AuthenticAMD uptodate rrrdFFF*
* package:
*swell-foop*
### Expected behavior
Should run as before.
### Actual behavior
Crashes with `"free(): invalid pointer"`
### Steps to reproduce the behavior
Just run from the console
Here's a stack backtrace:
```
Thread 1 "swell-foop" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden.
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007ffff7e0c55b in __GI_abort () at abort.c:79
#2 0x00007ffff7e64df8 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ffff7f70f3e "%s\n") at ../sysdeps/posix/libc_fatal.c:181
#3 0x00007ffff7e6c16a in malloc_printerr (str=str@entry=0x7ffff7f6f0e0 "free(): invalid pointer") at malloc.c:5332
#4 0x00007ffff7e6db3c in _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:4173
#5 0x000055555555f89f in tile_actor_construct (object_type=<optimized out>, tile=<optimized out>, texture=0x555556212e40, size=50) at src/25a6634@@swell-foop@exe/game-view.c:1979
#6 0x0000555555562697 in tile_actor_new (size=<optimized out>, texture=<optimized out>, tile=0x5555562a2b50) at src/25a6634@@swell-foop@exe/game-view.c:1993
#7 game_view_place_tiles (self=0x5555562aa490) at src/25a6634@@swell-foop@exe/game-view.c:697
#8 game_view_place_tiles (self=0x5555562aa490) at src/25a6634@@swell-foop@exe/game-view.c:545
#9 0x0000555555562cd7 in game_view_set_game (self=0x5555562aa490, value=<optimized out>) at src/25a6634@@swell-foop@exe/game-view.c:1545
#10 0x000055555556525c in swell_foop_real_startup (base=0x555556097150) at src/25a6634@@swell-foop@exe/swell-foop.c:946
#11 0x00007ffff7c9be82 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#12 0x00007ffff7c8aa72 in ?? () from /usr/lib/libgobject-2.0.so.0
#13 0x00007ffff7c8eac7 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#14 0x00007ffff7c8f92f in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#15 0x00007ffff733441a in g_application_register () from /usr/lib/libgio-2.0.so.0
#16 0x00007ffff733541a in ?? () from /usr/lib/libgio-2.0.so.0
#17 0x00007ffff733515a in g_application_run () from /usr/lib/libgio-2.0.so.0
#18 0x000055555555e1c0 in swell_foop_main (args=<optimized out>, args_length1=<optimized out>) at src/25a6634@@swell-foop@exe/swell-foop.c:1990
#19 0x00007ffff7e0ddeb in __libc_start_main (main=0x55555555c020 <main>, argc=1, argv=0x7fffffffe288, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe278) at ../csu/libc-start.c:308
#20 0x000055555555c05a in _start () at ../sysdeps/x86_64/start.S:120
```
My girlfriend is upset :)
Is it only here, or do you see the same problem?
prev parent reply other threads:[~2019-10-13 18:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 19:49 [ISSUE] " voidlinux-github
2019-09-15 19:53 ` voidlinux-github
2019-09-15 20:10 ` voidlinux-github
2019-09-15 20:25 ` voidlinux-github
2019-09-18 12:19 ` voidlinux-github
2019-09-18 12:43 ` voidlinux-github
2019-10-13 18:43 ` voidlinux-github [this message]
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=20191013184358.5AZQcIdbHOh2bgtQ35-dY2fMStou-GWt7DE7fNJq8Aw@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).