[zeromq-dev] Assertion failure in pull.cpp

Oliver Smith oliver at kfs.org
Sat Aug 21 08:14:30 CEST 2010

  On 8/20/2010 11:37 AM, Pieter Hintjens wrote:
> OK, I was using the wrong socket (!) in one of the test steps, which
> explains most of the problems I was seeing.  If one connects A rather
> than B, it's normal that writing to B won't do much.
*GRIN* Honestly - I keep running into the same thing every time I start 
a new up/downstream pair. Caveat: Because I was part of the discussion 
on the naming, I actively think "don't get this the wrong way around" 
and proceed to do exactly that :)

Again, I think this is a good case for having some debug-level warning 
mechanism where zeromq can provide more feedback when compiled with 
-DEBUG or something.

You'd have two copies of the zeromq library on your system, libzmq.a and 
libzmqdebug.a ... the options to build the latter would turn on the 
warning feedback system, so that more verbose output could be supplied 
when these kinds of issues occur. Great help for beginners and old hands 

me at mine$ ./testapp
Assertion failed: inpipe_ && !output_ (pull.cpp:39)
me at mine$ wtf?
Command 'wtf' not found.
me at mine$ g++ -o testapp testapp.cpp -lzmqdebug
me at mine$ ./testapp
testapp.cpp:35: Error: called recv() on a read only socket (type: 
Assertion failed: inpipe_ && !output_ (pull.cpp:39)
me at mine$ thanks!
Command 'thanks' not found.

More information about the zeromq-dev mailing list