Changes between Initial Version and Version 2 of Ticket #87

Timestamp:

Feb 12, 2014, 3:32:49 PM (10 years ago)

Author:

djay

Comment:

This issue should be fixed in r453, I simply added the message map the [lenv] section when it is created in the zoo_service_loader.c file.

If anything wrong occurs with the following modifications, please feel free to re-open this ticket or to open a new one.

Ticket #87
- Property Status changed from new to closed
- Property Resolution changed from to fixed
- Property Component changed from Development platform to zoo-kernel

Ticket #87 – Description

-                      initial
+                      v2
 The Zoo kernel provides the option to store a status message in shared memory along with the status value (i.e. the progress in percent), see this ticket: http://zoo-project.org/trac/ticket/81. However, the current implementation of updateStatus (service_internal.c, revision # 452) does not check if getMapFromMaps(conf,"lenv","message") returns NULL. A segmentation fault occurs (line 115) if a message value has not been set in the service code before a call to updateStatus:
+{{{
 // OK:
 setMapInMaps( conf, "lenv", "status", "99" );
 …
 setMapInMaps( conf, "lenv", "status", "99" );
 updateStatus( conf );
+}}}
 (Tested on a Window 7 system.)