From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: LMDB test failures under musl on mips
Date: Thu, 13 Feb 2014 22:42:23 +0100 [thread overview]
Message-ID: <20140213214223.GF23551@port70.net> (raw)
In-Reply-To: <20140213205040.GC19573@nodbug.moloch.sk>
* Martin Lucina <martin@lucina.net> [2014-02-13 21:50:40 +0100]:
> I'm currently using musl libc and LMDB [1] in a new project. When
> developing on a Debian x86_64 host everything works fine, but when building
> for a target device (OpenWRT mips or mipsel, I've tried both) with static
> linking my LMDB code starts failing with assertions and/or segfaults inside
> LMDB itself.
>
> Cross-compiling to statically linked musl on x86_64 does not have the
> problem.
>
> It's possible that the problem is LMDB itself; I can ask on the OpenLDAP
> lists but I'd like to check here first if someone else has encountered this
> problem?
>
mips was not nearly as extensively tested as x86 targets and
it has a lot of arch specific syscall quirks
so it may be a musl bug, if you have strace on the target
then please send a strace log
what is the pagesize used on the target?
(iirc some mips can be non 4k)
> You can reproduce the problem fairly easily by building the mtest* programs
> that come with LMDB. Running mtest a few times (after creating ./testdb)
> reliably gives either a segfault or various assertion failures in LMDB.
>
> Note that I'm using the prebuilt toolchains from musl.codu.org (thanks!),
> and the 0.9,15 release.
>
> Any ideas?
>
> Thanks,
>
> Martin
>
> [1] http://symas.com/mdb/
next prev parent reply other threads:[~2014-02-13 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 20:50 Martin Lucina
2014-02-13 21:39 ` Rich Felker
2014-02-13 21:42 ` Szabolcs Nagy [this message]
2014-02-13 23:26 ` Szabolcs Nagy
2014-02-14 9:31 ` Martin Lucina
2014-02-14 10:26 ` Szabolcs Nagy
2014-02-14 15:53 ` Martin Lucina
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=20140213214223.GF23551@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).