From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: musl mips 64 help (fwd)
Date: Tue, 16 Feb 2016 15:32:34 -0500 [thread overview]
Message-ID: <20160216203234.GY9349@brightrain.aerifal.cx> (raw)
I'm forwarding this to the list in case anyone else has ideas:
----- Forwarded message from Mahesh Bodapati <maheshbodapati90@gmail.com> -----
Date: Tue, 16 Feb 2016 18:40:23 +0530
Message-ID: <CAKd0kDLPFnFVO=y1yoHcBZVyrycbS1H4YvxuVswEMp7zhaLGMw@mail.gmail.com>
Subject: musl mips 64 help
From: Mahesh Bodapati <maheshbodapati90@gmail.com>
To: Rich Felker <dalias@libc.org>
Hi Rich,
We are getting FAIL with musl mips n64 dynamic build libraries and we
didn’t see issue with musl mips n64 static build libraries.
FAIL ./src/regression/pthread_cond-smasher.exe [status 1]
$ gdb ./src/regression/pthread_cond-smasher.exe
x136
settimeout(&ts);
B+ x137 int ret = condition_timedwait(&cond_main, &mut[phase],
&ts);
x138 tell("main seeing %u threads in phase %u, %s\n",
inside[phase], phase,
errorstring(ret));
B+>x139 if (ret) {
x140 t_error("main thread in phase %u (%u threads inside),
finished waiting: %s\n", phase, inside[phase],
errorstring(ret));
x141 return t_status;
x142
}
x143 }
(gdb) p ret
*$1 = 145*
(gdb) n
*(gdb) n*
*src/regression/pthread_cond-smasher.c:140: main thread in phase 0 (0
threads inside), finished waiting: Operation timed out*
(gdb)
What may be the cause for getting timeout with dynamic build which is
passing with static build.
----- End forwarded message -----
next reply other threads:[~2016-02-16 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 20:32 Rich Felker [this message]
2016-02-16 21:47 ` Szabolcs Nagy
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=20160216203234.GY9349@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).