Changes between Version 24 and Version 25 of FAQ


Ignore:
Timestamp:
Jan 13, 2011, 3:20:51 PM (10 years ago)
Author:
dtodd
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v24 v25  
    6666then you are at risk of having one of a number of problems.
    6767
    68 This is because mxa points to a an object that is contained within another object that has been made available for deletion.
     68This is because mxa points to a an object that is contained within another object that has been made available for deletion. In this example we are returning a transition table (TTable1D), which is an object that is contained within ACQ (an acquire1D object). The ACQ object will be released at the end of my_pulse_function() and therefore so will mx. When you try to use the return value, in this case mxa, in some other process (e.g. binning(mxa,...)), the behavior is unpredictable and usually bad.
    6969
    7070So far in our research we have see this situation cause these errors:
     
    7676    * Pointer to the correct value with no notification that it may not be valid the next time you look
    7777
    78 We list here a [gamma:SwigIssueSegfault detailed description of the problem and suggest some work arounds].
     78We list here a [gamma:SwigIssueSegfault detailed description of the problem and suggest some simple work arounds].