I'm trying to get the base libzmq running on a shiny new 64-bit windows 8.1
machine with cygwin, and I'm running into some issues trying to start with
autogen.sh. (I'm fairly certain that the 32-bit toolchain is doing the
building).
My setup may well be so far outside the box that this isn't worth worrying
about. But it seems like it's better to know about these things than not.
Then again, it may very well fall into the realm of "Some tests haven't
been ported for windows yet" or "Just use cmake and don't worry about the
tests."
After building the 3.2.3 release branch on cygwin (from the zeromq3-x
repo), running make check hangs at test_pair_ipc when it tries to call
bounce. Ctrl-C lets it exit.
So I tried the libzmq repo (commit 637f79419).
Before I installed libsodium, this is the part of make check that looks
interesting:
PASS: test_term_endpoint.exe
assertion "req_socket_events & ZMQ_EVENT_CLOSED" failed: file
"test_monitor.cpp", line 273, function: int main()
/bin/sh: line 5: 9688 Aborted (core dumped) ${dir}${tst
FAIL: test_monitor.exe
PASS: test_router_mandatory.exe
PASS: test_probe_router.exe
assertion "rc == 97" failed: file "test_stream.cpp", line 104, function:
void test_stream_to_dealer()
At that point, it seems to actually hang the shell. Ctrl-C doesn't seem to
do anything.
(Core dumps aren't actually created here).
After installing libsodium:
PASS: test_term_endpoint.exe
assertion "req_socket_events & ZMQ_EVENT_CLOSED" failed: file
"test_monitor.cpp", line 273, function: int main()
/bin/sh: line 5: 8936 Aborted (core dumped) ${dir}$tst
FAIL: test_monitor.exe
PASS: test_router_mandatory.exe
PASS: test_probe_router.exe
assertion "rc == 0" failed: file "test_stream.cpp", line 62, function: void
test_stream_to_dealer()
Stack trace:
Frame Function Args
/bin/sh: line 5: 7152 Aorted (core dumped) ${dir}$tst
...
FAIL: test_shutdown_stress.exe
The first time I run this, it hangs here.
I can Ctrl-C that and re-run make check. It produces the same output, but
Ctrl-C does not interrupt.
I added some debug printf statements. The first time, it got to the for
loop where it spins up the worker threads, then exited. Subsequent runs
seem to happen normally. So this could very well be the test that comes
next (test_pair_ipc).
On a 32-bit linux virtual box VM running on that host (with libsodium),
make check reports that:
...
test_stream: test_stream.cpp:104: void test_stream_to_dealer(): Assertion
`rc == 97' failed.
/bin/sh: line 5: 32125 Aborted ${dir}$tst
test_raw_sock: test_raw_sock.cpp:107: int main(): Assertion `rc == 97'
failed.
FAIL: test_stream
...
/bin/sh: line 5: 1118 Aborted ${dir}$tst
FAIL: test_raw_sock
(in both cases, I'm getting 54)
...
2 of 33 tests failed
Please report to zeromq-dev
On my standard 64-bit linux system, they run fine.
Does this seem worth opening up a github issue?
I'll work on what I can from my end, but this is my first attempt at
windows programming in years, and I'm really a total 0mq newb...I'm working
on my second pass through the Guide. So it seemed worth making an early
stage mention on the off-chance that someone else recognizes they symptoms.
Regards,
James
_______________________________________________
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
