Hello Ganesh,
To reproduce, start a fresh dispatcher on the trunk then create a listener and
delete it. The dispatcher will crashThe created listener should listen on the
same port as the amqp port (I know this should fail because the port is
reserved but it shouldn't crash).
qdmanage -b amqp://localhost:10401 create --type=listener role=inter-router
addr=localhost port=10401 name=localhost.10401.listener
authenticatePeer=falseqdmanage -b amqp://localhost:10401 delete --type=listener
--name localhost.10401.listener
Regards,Adel
> Date: Tue, 31 May 2016 10:27:48 -0400
> From: [email protected]
> To: [email protected]
> Subject: Re: [qpid-dispatch] Crash when trying to close a NULL listener
>
> Hi Adel,
> Can you please list the steps that caused this crash to occur? Would be
> great if you could send a reproducer.
> Thanks.
>
> ----- Original Message -----
> > From: "Adel Boutros" <[email protected]>
> > To: [email protected]
> > Sent: Tuesday, May 31, 2016 9:38:42 AM
> > Subject: [qpid-dispatch] Crash when trying to close a NULL listener
> >
> > Hello,
> > In qpid-dispatch, we have a core dump and a segmentation fault when a
> > qd_listener_t is being closed but it is NULL:
> > src/server.c:1614
> > void qd_server_listener_close(qd_listener_t* li){
> > qdpn_listener_close(li->pn_listener);
> >
> >
> >
> >
> >
> >
> >
> > }
> > A check on li would fix this crash.
> > Fix:void qd_server_listener_close(qd_listener_t* li){ if
> > (li) qdpn_listener_close(li->pn_listener);
> >
> >
> >
> >
> >
> >
> >
> > }
> > Regards,Adel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
