LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

data tooltips do not work in omp parallel for

Solved!
Go to solution

Hello NI,

it seems that data tooltips do not work, i.e., do not show any value within a parallized for loop, see below:

 

omg_data_tooltips.png

 

If the mouse is, e.g., in line 240, the value of index or spectrum_data_points is shown, if the mouse is in line 232 instead, no value shows. The same is true for x_data (line 235 versus line 241...)

 

Maybe I should add that the breakpoint was set after the loop in line 264.

0 Kudos
Message 1 of 6
(2,632 Views)

When hovering over an expression in debug mode, CVI asks the debugger to evaluate the expression. In this case, the debugger is unable to evaluate "x_data" in its scope on line 235. However, the evaluation works if you are suspended inside the for loop.

 

This is not a new behavior (not introduced in CVI 2019). I suspect it's not straightforward to fix, but we can file a bug report and give it a try if it bothers you. 

0 Kudos
Message 2 of 6
(2,606 Views)

Hi catalincocis,

thanks for the quick reply!

- I dit not say that this behaviour is new to CVI 2019 Smiley Wink

- I could understand that evaluating arrays is complicated in parallized sections, but it also does not work for simple variables as spectrum_data_points in line 232.

- yes, it bothers me because sometimes the workaround to find the variable outside the loop may require jumping to a code section far apart, so an attempt to improve on this is welcome Smiley Happy

0 Kudos
Message 3 of 6
(2,602 Views)

Hi catalincocis,

I am wondering if you filed a bug report - if so, what is the bug ID?

Thanks,

Wolfgang

@catalincocis wrote:
...I suspect it's not straightforward to fix, but we can file a bug report and give it a try if it bothers you. 
0 Kudos
Message 4 of 6
(2,565 Views)
Solution
Accepted by topic author Wolfgang

@Wolfgang wrote:

Hi catalincocis,

I am wondering if you filed a bug report - if so, what is the bug ID?

Thanks,

Wolfgang

@catalincocis wrote:
...I suspect it's not straightforward to fix, but we can file a bug report and give it a try if it bothers you. 

 

Hi Wolfgang,

 

The bug ID is 739395.

0 Kudos
Message 5 of 6
(2,553 Views)

Thanks Smiley Happy

0 Kudos
Message 6 of 6
(2,549 Views)