W Walter Brunmueller Member Licensed User Longtime User Aug 29, 2015 #1 Hello! Summary: In the attachments I gave you two sourcecodes and two screenshots. attachment 1: 'MayaCal_not_OK.zip' is the codesample witch calculates wrong results. In the screenshot 1 'Maya_Result_not_OK.jpg' you can see the results. attachment 2: 'MayaCal_OK.zip' is the codesample witch calculates right results. In the screenshot 2 'Maya_Result_not_OK.jpg' you can see the results. To get the right result I do only a multiplication by '1' in one line of the code. Reproduction Steps: 1. start the project from 'MayaCal_not_OK.zip' in 'debug rapid' mode 2. press the button on the display 3. Wait for the brakepoint in line 347 (it takes a long time - large loop) 4. Now you can check the result e.g. Kalender.Entry(364) Actual Behavior: look at the screenshot 2 'Maya_Result_not_OK.jpg' Expected Behavior: look at the screenshot 1 'Maya_Result_OK.jpg' Additional information: I guess, that the compiler generates only a reference for val_28TageKIN to val_260er. So both values have always the same value. If I do a multiplication by '1' the compiler have to generate an extra variable for both regards Walter Attachments MayaCal_not_OK.zip MayaCal_not_OK.zip 152.5 KB · Views: 289 Maya_Result_not_OK.jpg 146.3 KB · Views: 297 MayaCal_OK.zip MayaCal_OK.zip 150.4 KB · Views: 274 Maya_Result_OK.jpg 162.3 KB · Views: 331
Hello! Summary: In the attachments I gave you two sourcecodes and two screenshots. attachment 1: 'MayaCal_not_OK.zip' is the codesample witch calculates wrong results. In the screenshot 1 'Maya_Result_not_OK.jpg' you can see the results. attachment 2: 'MayaCal_OK.zip' is the codesample witch calculates right results. In the screenshot 2 'Maya_Result_not_OK.jpg' you can see the results. To get the right result I do only a multiplication by '1' in one line of the code. Reproduction Steps: 1. start the project from 'MayaCal_not_OK.zip' in 'debug rapid' mode 2. press the button on the display 3. Wait for the brakepoint in line 347 (it takes a long time - large loop) 4. Now you can check the result e.g. Kalender.Entry(364) Actual Behavior: look at the screenshot 2 'Maya_Result_not_OK.jpg' Expected Behavior: look at the screenshot 1 'Maya_Result_OK.jpg' Additional information: I guess, that the compiler generates only a reference for val_28TageKIN to val_260er. So both values have always the same value. If I do a multiplication by '1' the compiler have to generate an extra variable for both regards Walter
Erel B4X founder Staff member Licensed User Longtime User Aug 30, 2015 #2 Does it work properly in Release mode? Can you try to reproduce it in a smaller project?
W Walter Brunmueller Member Licensed User Longtime User Aug 30, 2015 #3 Hello Erel! I cannot reproduce this in an smaller project. In release mode the result is right!! The problem is only in debug mode
Hello Erel! I cannot reproduce this in an smaller project. In release mode the result is right!! The problem is only in debug mode
W Walter Brunmueller Member Licensed User Longtime User Aug 30, 2015 #4 An additional information!! The problem only occurs if a brakepoint ist set!!! And only in 'debug rapid' mode!
An additional information!! The problem only occurs if a brakepoint ist set!!! And only in 'debug rapid' mode!