Hmmm, I'm not sure where that pointer comes from. I added print statements to ffi-rzmq showing all socket pointers, and their addresses for new sockets and calls to getsockopt. At the end of these gists is the GDB backtrace.
Output under Rubinius: https://gist.github.com/822990 <https://gist.github.com/822990>Output under 1.9.2: https://gist.github.com/823012 I don't see that value anywhere. I'm not a C/C++ programmer by trade, so perhaps there's something I'm not following. It should be noted that 1.9.2 and Rubinius have different FFI implementations. On Fri, Feb 11, 2011 at 1:49 AM, Martin Sustrik <[email protected]> wrote: > Hi Andrew, > > > #4 0x00007ffff4d3405e in zmq::socket_base_t::getsockopt (this=0x3dd5, >> option_=<value optimized out>, optval_=0x7fffec000a30, optvallen_=<value >> optimized out>) >> > > This=0x3dd5 doesn't seem to be a valid pointer. Are you sure you are not > passing a bogus pointer of 0MQ from the binding? > > Martin > -- Andrew Cholakian http://www.andrewvc.com
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
