RE: [JDEV] Bug report.. UPDATE!!

["Thomas Charron" <tcharron@nermail.ups.com>]

	Yes another update..  I'll now hand this over to you guys..  The error is
becouse of a call to XML_ParserFree(xp->parser); in free_xptpool.

	Actually, I can now tellyou exactly what it is (As I was writing the above
it hit me like a brick..)

	xpt_packet_new, which creates the parser for a connection, isn't called
untill the dispatch loop in handle.c.  And it isn't called untill there is a
call to dispatch with an IO_NORMAL flag.  When a disconnection comes before
ANY data is sent over the line, there IS no call to xpt_packet_new, and
hence causes XML_ParserFree to belch as it attempts to free something that
isn't there..

	I'd love to trouble shoot it further, but I glanced at XMLParserFree, and
I'm not that familiar with the inner workings of xmlparse.c.  Could we
simply have xpt_packet_new as soon as a connection is made, instead of
checking for it every time dispatch is called?
--
Thomas Charron
United Parcel Service
Northeast Region
"Moving at the speed of a T3 Trunk Line!"


> -----Original Message-----
> From: owner-jdev@jabber.org [mailto:owner-jdev@jabber.org]On Behalf Of
> Thomas Charron
> Sent: Monday, April 12, 1999 1:46 PM
> To: Jabber Development
> Subject: [JDEV] Bug report..
>
>
> 	Just found a little bug..  Sorry I don't have any server
> source in front of
> me, but here's what happens..
>
> 	Connect to jabber.transport.  Before sending ANYTHING,
> disconnect..  Watch
> the segfaults fly in the transport..
>
> 	This can be done by just telnet 5222, and upon the connection being
> accepted, disconnect..
>
> --
> Thomas Charron
> United Parcel Service
> Northeast Region
> "Moving at the speed of a T3 Trunk Line!"
>