RE: [dsdp-tcf-dev] TCF assertion error

["Tarassov, Eugene" <eugene.tarassov@xxxxxxxxxxxxx>]

Hi Sam,

 

It looks like that bug was fixed March 04, 2009. SVN log says:

Revision: 633
Author: eutarass
Date: 2:44:51 PM, Wednesday, March 04, 2009
Message:
Fixed: TCF Agent: Exception in message handler could cause assert failure.

 

Also, what you call old agent appears to be built from newer source code, because message "Exception in message handler: 131074 JSON syntax error" is a newer version of "Exception handling protocol message: 131074 JSON syntax error".

Regards,

Eugene

---

From: dsdp-tcf-dev-bounces@xxxxxxxxxxx [mailto:dsdp-tcf-dev-bounces@xxxxxxxxxxx] On Behalf Of Quiring, Sam
Sent: Wednesday, October 07, 2009 2:16 PM
To: dsdp-tcf-dev@xxxxxxxxxxx
Subject: [dsdp-tcf-dev] TCF assertion error

Greetings,

 

Martin Oberhuber told me to send this to this list.

 

We have a client-server architecture that uses TCF.  A stand-alone agent runs on the target as a server.  I've been using an agent built from TCF sources that are at least a year old.  Yesterday I upgraded to new sources from spring 2009.  At the same time I upgraded the sources for all pieces of the architecture and rebuilt all the components.  I have a test that is getting a TCF assertion error when I run with the new agent, but not with the old agent. 

 

Here is the invocation of the agent with the assertion error shown in red:

 

> ./stp-atspi -i -L ~/tmp/wlog

> stp-atspi: channel_tcp.c:106: delete_channel: Assertion `c->ibuf.handling_msg

== HandleMsgTriggered' failed

 

Note: this assertion seems to cause the agent to die.

 

Here's the TCF log from this run.  The lines in red (also marked with a +) are not present when I run the old agent:

 

  TCF 35:27.068: read Locator: application(Prizm)
  TCF 35:27.068: Exception handling command STPAgent.findTopWindow: 131074 JSON syntax error
  TCF 35:27.069: Exception handling protocol message: 131074 JSON syntax error
  TCF 35:27.069: Closing channel 0x086bc690 TCP:192.168.175.1:3716
  TCF 35:27.069: close_stp_event_handler() - bye
  TCF 35:27.069: channel server disconnected

+ TCF 35:27.069: Socket is shutdown by remote peer, channel 0x086bc690 TCP:192.168.175.1:3716
+ TCF 35:27.069: Closing channel 0x086bc690 TCP:192.168.175.1:3716
  TCF 35:27.069: Deleting channel 0x086bc690

 

 

I still have the old agent built with older TCF sources.  When I run it under identical circumstances I do not get an assertion

error and I do not get the two lines marked with + in the above log:

 

 

TCF 34:14.200: read Locator: application(Prizm)
TCF 34:14.200: Exception handling command STPAgent.findTopWindow: 131074 JSON syntax error
TCF 34:14.200: Exception in message handler: 131074 JSON syntax error
TCF 34:14.200: Closing channel 0x0910a7a0 TCP:192.168.175.1:3701
TCF 34:14.202: close_stp_event_handler() - bye
TCF 34:14.202: channel server disconnected

TCF 34:14.202: Deleting channel 0x0910a7a0 

 

-Sam