FLAM® Issue Tracker

View Revisions: Issue #891 All Revisions ] Back to Issue ]
Summary 0000891: Make record and byte interface thread save
Revision 2017-10-13 16:05 by Ulrich Schwab
Description For the byte interface new entries will be implmented which are thread save but do not conform to the standard I/O interface.

For the record interface the current return code will be interpreted as a pointer to a structure of two shorts (16 bit values), with the first 16 bit containing the space for the error trace and the second short containing the return code. If the first short (high order half word) is not 0 then after the first 4 byte a remaining byte array can be used to store the error trace. This removes the global variable currently used to get the error trace later with a second call, which is not a thread save solution.
Revision 2017-10-13 14:19 by Falk Reichbott
Description For the byte interface new entries will be implmented which are thread save but not conform with the standard I/O interface.

For the record interface the current return code will be interpreted as a pointer to a structure of two shorts (16 bit values), where the first 16 bit contains the space for the error trace and the second short contains the return code. If the first short (high oder half word) not 0 then after the first 4 byte a remining byte array can be filled up with the error trace. This removes the global variable currently implemented to get the error trace later in a second call, which is not a thread save solution.


Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker