Take a look here: http://www.zeromq.org/docs:issue-tracking
Without the zmq_msg_close() call, you will likely leak memory. cr On Jan 11, 2013, at 12:23 PM, A. Mark <[email protected]> wrote: > > Thanks Charles, > > Not sure how to open an issue...by the way it looks like if I remove the > zmq_msg_close it works OK. > > On Fri, Jan 11, 2013 at 9:43 AM, Charles Remes <[email protected]> wrote: > > On Jan 11, 2013, at 11:32 AM, "A. Mark" <[email protected]> wrote: > > > The segfault occurs in the first iteration (i=0) with message_size=8MB, > > with message_size < 1MB no issues. Itl looks like heap corruption, but I > > investigated no further. > > Unless this is a library issue I don't know if I'm doing anything illegal > > here. > > You should be able to allocate messages of any size. If you have a small > program that reliably reproduces this segfault, please open an issue and > attach the code. > > cr > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
