[rabbitmq-discuss] Program crashes in amqp_abort() on HP-UX 11.31

Mon Jul 8 08:11:57 BST 2013

Hi there

My application uses  library rabbitmq-c and sometimes it crashes on HP-UX
11.31 with below stack:
#0 0xc00000000054bc70:0 in _waitpid_sys+0x30 () from /lib/hpux64/libc.so.1
#1 0xc000000000562b80:0 in waitpid ()
#2 0xc00000000a3d9e00:0 in <unknown_procedure> + 0xa0 ()
#3 0xc00000000a3da280:0 in <unknown_procedure> + 0x90 ()
#4 <signal handler called>
#5 0xc000000000211ab0:0 in _lwp_kill+0x30 () from
/lib/hpux64/libpthread.so.1
#6 0xc000000000178810:0 in pthread_kill ()
#7 0xc0000000003f8140:0 in raise ()
#8 0xc000000000508d00:0 in abort ()
#9 0xc0000000043df860:0 in amqp_abort (
#10 0xc0000000043e06f0:0 in amqp_handle_input (state=0x600000000480bc60, 
#11 0xc0000000043e1fe0:0 in wait_frame_inner (state=0x600000000480bc60, 
#12 0xc00000000a9b4ad0:0 in RabbitMQ::RabbitMQQueueImpl::recv (
#13 0xc00000000a992ee0:0 in consumer_impl::execute (this=0x600000000428edf8)
#14 0xc00000000a436af0:0 in threads::thread_proc(void*)+0x1c0 ()
#15 0xc00000000013fb20:0 in __pthread_bound_body () 

And in log file I can see following message:
Failed to start consumer with configurationInternal error: invalid
amqp_connection_state_t->state 0

So as I understand, I get corrupted packet and as a result abort is called
from amqp_abort.

I think it isn't a good idea to call abort into library because my
application is crashed and I can't 
managed this situation (for example clean resources and reconnect or
something else).

Is it possible to remove abort function from library?

--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Program-crashes-in-amqp-abort-on-HP-UX-11-31-tp27878.html
Sent from the RabbitMQ mailing list archive at Nabble.com.