Skip to content

Instantly share code, notes, and snippets.

View est31's full-sized avatar

est31

View GitHub Profile
Program received signal SIGSEGV, Segmentation fault.
__memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
36 ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: File not found
(gdb) bt full
#0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:36
No locals.
#1 0x00007ffff58e65e0 in std::basic_streambuf<char, std::char_traits<char> >::xsputn(char const*, long) ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
No symbol table info available.
#2 0x00007ffff58dddb5 in std::basic_ostream<char, std::char_traits<char> >& std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char const*, long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
Program received signal SIGSEGV, Segmentation fault.
0x0000000001132130 in ?? ()
(gdb) bt
#0 0x0000000001132130 in ?? ()
#1 0x00000000007cda38 in irr::gui::CGUIEnvironment::OnPostRender(unsigned int) ()
#2 0x000000000064398a in draw_load_screen (text=..., device=device@entry=0xf12c30, guienv=guienv@entry=0x10350e0,
font=font@entry=0x107f190, dtime=dtime@entry=0, percent=percent@entry=0, clouds=clouds@entry=true)
at ~/src/minetest/src/drawscene.cpp:545
#3 0x000000000066426d in the_game (kill=@0xeaa7e0: false, random_input=random_input@entry=false, input=input@entry=0x1025950,
@est31
est31 / backtrace
Created October 26, 2014 18:01
backtrace for MT segfault
#0 0x00007ffff4f9dbb9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007ffff4fa0fc8 in __GI_abort () at abort.c:89
#2 0x00007ffff4fdae14 in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x7ffff50e9668 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#3 0x00007ffff4fe70ee in malloc_printerr (ptr=<optimized out>, str=0x7ffff50e9830 "double free or corruption (fasttop)", action=1)
at malloc.c:4996
#4 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3840
#5 0x00007ffff5904046 in std::string::reserve(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6 0x00000000006d1873 in push_back (__c=115 's', this=0xe8b348 <errorbuf+72>) at /usr/include/c++/4.8/bits/basic_string.h:1056
@est31
est31 / password_list.txt*outdated*
Last active August 29, 2015 14:14
pwm example (old format)
return {["passwords"] = { --the list of the passwords. Every password has an ID. Every entry references that ID instead of the password itself.
[42] = "42world",
[33] = "12345secretpassword",
[34] = "anothersupersecretpassword"
}, ["lu"] = {
["user1"] = { --every username gets one entry
["addr_lu"] = { --you can either specify the domain name in the "addr_lu" section,
--or you can specify the "display name" (or both) in the "select_srv_lu" section.
["digitalaudioconcepts.com"] = {["30001"] = 33},
["0.0.0.0"] = {["30000"] = 42} --a localhost test client. Note the changed number, its a changed ID.
@est31
est31 / password_list.txt
Last active August 29, 2015 14:14
pwm config example
return {["password_list"] = {
{user="est31", address="digitalaudioconcepts.com", port=30001, password="secretpassword", comment="The first Server I logged on"},
{user="est31", password="anothersecretpassword", name="Xanadu", comment="Some other nice server"},
{user="est31", address="0.0.0.0", port=30000, password="", comment="Empty password for local sessions"},
{user="est", address="0.0.0.0", port=30000, password="", comment="Empty password for local sessions"}
}}
@est31
est31 / init.lua
Last active August 29, 2015 14:15
crafting speed test
-- file maintained at https://gist.github.com/est31/e477d9a624dced5cb274
-- tests basic crafting speed
local function crafting_loop()
local x = minetest.get_us_time()
local cnt = 20000
local locnt = 50
while cnt ~= 20000-locnt do
minetest.get_craft_result({
input = "normal",
@est31
est31 / stats.lua
Last active August 29, 2015 14:18
craft stats script
-- put this into some builtin/game/*.lua file
-- it will print craft stats for the mod config to stdout when you start a world.
local register_craft_old = core.register_craft
core.type_stats = {}
core.grouped_number = 0
core.non_grouped_number = 0
local function is_group_str(val)
return string.sub(val, 1, 6) == "group:"
end
core.register_craft = function(params)
@est31
est31 / openproject_wiki_extractor.md
Last active January 28, 2016 04:08
How to extract wiki pages from openproject and to bring them into more suitable format.

Exporting openproject wiki files

The following guide explains how to export an openproject wiki to somewhat readable openproject syntax-ed files.

The guide assumes you are running in bash shell, and can use GNU sed, and that you have the sqlite3 command utility installed.

Following UN*X philosophy, all commands should be silent and have no stdout. If you get something printed to stdout there is an error.

Part 0: Preparation

Looking back and looking forward -- Rust in 2017 and 2018

Recently, there had been a call for blog posts reflecting 2017 and about which path Rust should choose in 2018.

First a few words about me. I was and still am a student, and most of my coding is for learning and because it is fun. Also, coding is a great excuse for procrastinating something more important :). Having contributed to open source codebases has helped me determine that I want to do this in a day job once I'm done with my studies.

I've heard about Rust somewhere around the 1.0 release in 2015. I don't know the details any more, but most likely it was a German tech news website. I've then read on about what Rust is and its promises like zero cost abstractions, fearless concurrency or the concept of safety really stood out. My background was C++ so I also quite liked the syntax. A bit later I decided to read the the book (first edition, back then

@est31
est31 / Releasing_godot_for_fdroid.md
Last active September 27, 2018 11:41
A collection of things to do in order to be nice to f-droid packagers

How to release a godot application for f-droid

In the best case, you should:

  1. tag your releases. This way, one always knows which commit to package for a specific release
  2. create and maintain an export.cfg, with an icon, and version numbers raised at each release

Explanations why these things are useful for packagers, and how they are done, and done best, can be found below.