[zeromq-dev] OpenPGM & segfault - assertion failed

[Olivier]

I wonder, if using "epgm://224.0.0.1:5555" to connect (as i do) instead
of "epgm://eth0;224.0.0.1:5555" could be a reason of these crashs ?

Because i can't see anywhere in the doc an example with the same string
i used. 
http://api.zeromq.org/zmq_pgm.html 
http://www.zeromq.org/docs:cookbook


I'm using it, because the second one (with interface name), generate an
assertion fail on my node :
"Assertion failed: false (pgm_socket.cpp:130)"
This because pgm return an error EAGAIN (if i don't make mistake).

So i've avoid the problem by using "epgm://224.0.0.1" to connect, and it
works (more or less, there are still these segfaults).


Olivier.


Le mardi 11 mai 2010 à 21:03 +0800, Steven McCoy a écrit :
> On 11 May 2010 20:50, Steven McCoy <steven.mccoy at miru.hk> wrote:
>         Ok, reproducing crashing is easy enough, getting gdb to work
>         with zmq is not so easy.
>         
>         
> 
> 
> Rebuilding with CFLAGS="-g -O0" CXXFLAGS="-g -O0" seems to work,  now
> is this purely a zeromq issue first:
> 
> 
> (gdb) print *mru_decoder
> $11 = {<zmq::decoder_t<zmq::zmq_decoder_t>> = {
>     read_pos = 0x401aa005c7 <Address 0x401aa005c7 out of bounds>,
> to_read = 558076263070,
>     next = 0x4000000000, bufsize = 9165358252710428672,
>     buf = 0x401aa00000 <Address 0x401aa00000 out of bounds>},
> destination = 0x81f0900000,
>   tmpbuf = "\000\000\000\000@\000\000", in_progress = {content = 0x0,
> flags = 0 '\0',
>     vsm_size = 0 '\0',
>     vsm_data = "\000L▒▒1\177\000\000▒\032@", '\0' <repeats 13 times>,
> "▒Y\204\000e"}}
> 
> 
> Those pointers and counters are very messed up.
> 
> 
> -- 
> Steve-o 
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev