Hello Reneir, This regarding the bug 1794430 (Avoid duplicate alarms and \\\"blank\\\" alarms from entering).
This bug is not fixed in openhpi-2.11 branch. I would like to know whether this bug is getting fixed. If not, I can take it up and try to fix. I'm analysing the bug and could able to make some progress. I could able to find the root cause of 'blank' alarms. The oh_add_alarm (openhpid/alarm.c +124) is causing the blank alarms to be put into the file. The oh_add_alarm is called by oh_detect_oem_event_alarm function (openhpid/alarm.c +352) for creating (allocating memory) the alarm structure and filling some of the fields. The same logic is also present in oh_detect_resource_event_alarm, oh_detect_sensor_event_alarm and oh_detect_resource_alarm functions. These functions calls oh_add_alarm with 3rd parameter set to 0 (means save the alarm to file). Hence, whenever the oh_detect_oem_event_alarm (or oh_detect_resource_event_alarm or oh_detect_sensor_event_alarm or oh_detect_resource_alarm) gets executed, a blank alarm gets inserted into DAT file. Regards, Raghavendra PG ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
