When debugging package, local variables always listed as 'null'

When I'm debugging a package procedure, if I try to inspect any local variables by hovering the mouse cursor over them, the floating text that appears always says they're set to null - even though I know (because the procedure works as expected) that there must be a value there. Also, local variables don't appear in the 'Data' debug tab; and if I drag the local variables into the 'Watch' tab, their value is listed as null.
Using v1.1.2.25 against a 9.2.0.6 db - anyone have any ideas..?
Cheers,
James

Local variables should be used whenever you need a value only in a single method and don't need to remember it's value between two invocations of that method.
A perfect example would be the counter in a for-loop.

Similar Messages

Kodo 3.0.3 fails when detaching package local classes

When I try to detach a class that is package local to enforce usage of
factories and interfaces Kodo
throws the following exception:
kodo.util.UserException: Cannot access the detached state of class "class
xxx.core.model.competitor.CompetitorImpl". Ensure that the class has the
"detachable" metadata extension, and the the class has been re-enhanced.
NestedThrowables:
java.lang.IllegalAccessException: Class kodo.runtime.KodoHelper can not
access a member of class xxx.core.model.competitor.CompetitorImpl with
modifiers "public final"
at kodo.runtime.KodoHelper.setDetachedState(KodoHelper.java:496)
at kodo.runtime.DetachManager.setDetachedVariables(DetachManager.java:231)
at kodo.runtime.DetachManager.detach(DetachManager.java:168)
at kodo.runtime.DetachManager.detach(DetachManager.java:55)
at
kodo.runtime.PersistenceManagerImpl.detach(PersistenceManagerImpl.java:3073)
at
xxx.core.model.competitor.CompetitorImplTest.doCheckPersistent(CompetitorImp
lTest.java:798)
at xxx.core.model.DatabaseTest.checkPersistent(DatabaseTest.java:133)
at xxx.core.model.DatabaseTest.testPersistence(DatabaseTest.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
..java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at com.intellij.rt.execution.junit2.IdeaJUnitAgent.doRun(Unknown Source)
at
com.intellij.rt.execution.junit.TextTestRunner2.startRunnerWithArgs(Unknown
Source)
at
com.intellij.rt.execution.junit2.JUnitStarter.prepareStreamsAndStart(Unknown
Source)
at com.intellij.rt.execution.junit2.JUnitStarter.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
..java:25)
at com.intellij.rt.execution.application.AppMain.main(Unknown Source)
Caused by: java.lang.IllegalAccessException: Class kodo.runtime.KodoHelper
can not access a member of class xxx.core.model.competitor.CompetitorImpl
with modifiers "public final"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:57)
at kodo.runtime.KodoHelper.invoke(KodoHelper.java:625)
at kodo.runtime.KodoHelper.setDetachedState(KodoHelper.java:491)
... 38 more
NestedThrowablesStackTrace:
java.lang.IllegalAccessException: Class kodo.runtime.KodoHelper can not
access a member of class xxx.core.model.competitor.CompetitorImpl with
modifiers "public final"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:57)
at kodo.runtime.KodoHelper.invoke(KodoHelper.java:625)
at kodo.runtime.KodoHelper.setDetachedState(KodoHelper.java:491)
at kodo.runtime.DetachManager.setDetachedVariables(DetachManager.java:231)
at kodo.runtime.DetachManager.detach(DetachManager.java:168)
at kodo.runtime.DetachManager.detach(DetachManager.java:55)
at
kodo.runtime.PersistenceManagerImpl.detach(PersistenceManagerImpl.java:3073)
at
xxx.core.model.competitor.CompetitorImplTest.doCheckPersistent(CompetitorImp
lTest.java:798)
at xxx.core.model.DatabaseTest.checkPersistent(DatabaseTest.java:133)
at xxx.core.model.DatabaseTest.testPersistence(DatabaseTest.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
..java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at com.intellij.rt.execution.junit2.JUnitStarter.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
..java:25)
at com.intellij.rt.execution.application.AppMain.main(Unknown Source)
Seems that KodoHelper tries to access something per reflection and fails
because the class is
not public and setAccessible(true) is not used.
When the class is changed to be public detaching seems to work fine.

Werner-
You are correct: Kodo is using reflection to set the detached state in
the object. We will make a note of this in the documentation. For the
time being, the object will need to be public (you can help enforce a
factory pattern by having a protected constructor).
This will be addressed when we implement the final version of JDO 2.0,
which will have a more well-defined specification for how detachment is
to work.
In article <[email protected]>, werner wrote:
When I try to detach a class that is package local to enforce usage of
factories and interfaces Kodo
throws the following exception:
kodo.util.UserException: Cannot access the detached state of class "class
xxx.core.model.competitor.CompetitorImpl". Ensure that the class has the
"detachable" metadata extension, and the the class has been re-enhanced.
NestedThrowables:
java.lang.IllegalAccessException: Class kodo.runtime.KodoHelper can not
access a member of class xxx.core.model.competitor.CompetitorImpl with
modifiers "public final"
at kodo.runtime.KodoHelper.setDetachedState(KodoHelper.java:496)
at kodo.runtime.DetachManager.setDetachedVariables(DetachManager.java:231)
at kodo.runtime.DetachManager.detach(DetachManager.java:168)
at kodo.runtime.DetachManager.detach(DetachManager.java:55)
at
kodo.runtime.PersistenceManagerImpl.detach(PersistenceManagerImpl.java:3073)
at
xxx.core.model.competitor.CompetitorImplTest.doCheckPersistent(CompetitorImp
lTest.java:798)
at xxx.core.model.DatabaseTest.checkPersistent(DatabaseTest.java:133)
at xxx.core.model.DatabaseTest.testPersistence(DatabaseTest.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at com.intellij.rt.execution.junit2.IdeaJUnitAgent.doRun(Unknown Source)
at
com.intellij.rt.execution.junit.TextTestRunner2.startRunnerWithArgs(Unknown
Source)
at
com.intellij.rt.execution.junit2.JUnitStarter.prepareStreamsAndStart(Unknown
Source)
at com.intellij.rt.execution.junit2.JUnitStarter.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at com.intellij.rt.execution.application.AppMain.main(Unknown Source)
Caused by: java.lang.IllegalAccessException: Class kodo.runtime.KodoHelper
can not access a member of class xxx.core.model.competitor.CompetitorImpl
with modifiers "public final"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:57)
at kodo.runtime.KodoHelper.invoke(KodoHelper.java:625)
at kodo.runtime.KodoHelper.setDetachedState(KodoHelper.java:491)
... 38 more
NestedThrowablesStackTrace:
java.lang.IllegalAccessException: Class kodo.runtime.KodoHelper can not
access a member of class xxx.core.model.competitor.CompetitorImpl with
modifiers "public final"
at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:57)
at kodo.runtime.KodoHelper.invoke(KodoHelper.java:625)
at kodo.runtime.KodoHelper.setDetachedState(KodoHelper.java:491)
at kodo.runtime.DetachManager.setDetachedVariables(DetachManager.java:231)
at kodo.runtime.DetachManager.detach(DetachManager.java:168)
at kodo.runtime.DetachManager.detach(DetachManager.java:55)
at
kodo.runtime.PersistenceManagerImpl.detach(PersistenceManagerImpl.java:3073)
at
xxx.core.model.competitor.CompetitorImplTest.doCheckPersistent(CompetitorImp
lTest.java:798)
at xxx.core.model.DatabaseTest.checkPersistent(DatabaseTest.java:133)
at xxx.core.model.DatabaseTest.testPersistence(DatabaseTest.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at com.intellij.rt.execution.junit2.JUnitStarter.main(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at com.intellij.rt.execution.application.AppMain.main(Unknown Source)
Seems that KodoHelper tries to access something per reflection and fails
because the class is
not public and setAccessible(true) is not used.
When the class is changed to be public detaching seems to work fine.
Marc Prud'hommeaux
SolarMetric Inc.

Can you sort the "local variable" pick list?

My program has a lot of local variables. If I right click on a variable and click on "select item", a loooong list of all my local variables appears. They appear to be in the order in which they were created in my program.
Is there any way to modify the display to where the local variables appear in alphabetical order?
Amateur programmer for over 10 years!

The best solution is to not use a lot of local variables . Here is a neat trick to use local variables without having to use local variables . If you are using a state machine (case structure inside a while loop), create a cluster constant on the block diagram inside a state or case called "Local Defs". Inside the cluster, put constants for every local variable you will use. Label the constants like you would a local variable. Put a shift register on the loop border. Wire the cluster to the shift register on the right side. Do not initialize the shift register on the left side. In any case frame, you can wire from the left shift register into an unbundle or bundle to read or write to the Local. You never have to call the Local Defs state, the cluster will be defined because of the wiring. If using controls at many places, make a local constant for each control and have a state where the control is written to the local. Then you can read the local to use the value at any time. See attached vi for an example.
- tbob
Inventor of the WORM Global
Attachments:
StateMachineWithLocals.vi ‏45 KB

Debugging and Local Variable

Hi All
In MS visual studio i can select a local variable (Promise I will go and wash my mouth out now) and add it to a watch therefore i can see what the value of the variable as I go through the code line for line
how can I view local variable in xcode ?
Regards
Tony

To do something similar in Xcode, select the variable and either choose Run > Variables View > View Variables as Expression or choose Run > Variables View > View Variable in Window. Both options place the local variable in a separate window for you to view.
There's not much difference between the two options if you're viewing one variable, but there is a difference if you're viewing multiple variables. If you view the variable as an expression, Xcode places all the variables you want to view in one Expressions window. If you view the variable in a window, Xcode creates a new window when you choose Run > Variables View > View Variable in Window.

Debug - tracking local variables

Hi,
I don't find the possibiliy to see the values of local variables of my procedures.
Can you tell me how?
Thanks
Silke

If you have error in your code and didn't compile, it will add breakpoint in that line of your last compiled version.
If it is not that, try cleaning your project in Project -> Clean

Make list of names in local variable list appear in alphabetical order?

When you select a variable name from the drop down list of a local variable the list appears to be in chronological order. Is there any to make this list appear in alphabetical order?
George

Hi George:
You said that local variables list appears in chronological order, but you wanted to appear in alphabetic order.
You just need to set apropiate names and then use SetTabbingOrder
You can use SetTabbingOrder to order all controls and indicators of your front panel, treating every control you see in the block diagram as one
(A cluster is one of the controls you can order, but the elements inside the cluster must be ordered with ReorderControlsInCluster right-clicking the cluster)
Returning. To SetTabbingOrder you have to click on VI's EDIT menu and select Set Tabbing Order.
The front panel will turn it's color to somethin darker, and every control will be shown with a number.
That number is it's tabbing index.
At the beginning you see a 0 in the top, that means that if you click in a control, that control will become number 0, and then the number it the top will pass to be 1, so you can select the next control in order.
If your first 23 elements are ordered, you don't need to click all 23, you can just set the top number to 23 and continue ordering.
When you reorder an element, all elements before that remain the same, and the rest are added by one.
When you are don, click on OK, or discard changes with x
This SetTabbingOrder you can do with elements in your front panel, can be done with elements into a cluster and elements into a Tab Control. Only change de name (in clusters is "Reorder controls in cluster" and in Tabs is "Reorder controls in page"), but they work the same
You might be interested in reordering in groups than reordering alphabetically?
Hope it helps,
Aitortxo.

Default initialisation of member variables and local variables

I don't understand why member variables are initialized with default values by Java.
Objects are initialized with "null" and primitives with "0", except boolean, which is initialized with "false".
If these variables are used locally they are not initialized. The compiler requires them to be initialized by the programer, for example "String s = null".
Why? What is the use of that difference?
And why are arrays always initialized with default values, no matter if they are member variables or local variables? For example String[] s = new String[10]; s[0] to s[9] are initialized with "null", no matter if "s" is a local or member variable.
Can someone please explain that strange difference, why it is used? To me it has no sense.

Most of the time I have to initialize a local variable
with "String s = null" in order to use it because
otherwise the compile would complain. This is a cheap
little trick, but I think everyone uses it.
I wouldn't agree with "most of the time". The only cases where it is almost necessary to do that is when the variable should be initialized in a loop or a try-catch statement, and that doesn't happen too often.
If local variables were initiliazed automatically without a warning it would be a Bad Thing: the compiler could tell when there is a possibility that a variable hasn't been assigned to and prevent manymanymany NullPointerExceptions on run time.
And you didn't answer me why this principle is not
used with arrays if it is so useful as you think.
Possibly it is much more difficult to analyse the situation in the case of arrays; what if values are assigned to the elements in an order that depends on run time properties such as values returned from a random number generator.
The more special rules one has to remember, the more
likely one makes errors.I agree, but what is the rule to remember in this case?

Question about Local Variables (Multiple answers welcomed!)

A couple of questions about Local Variables
1. Programmers always say: “Do not abuse of Local Variables”. I’d like to know, when and where Local variable are most efficiently used?
2. If I have to create a couple of local variables, is there anyway to “clone” them without going through the repetitive “create/local variables” mouse click each time? (When I try to copy and paste, it creates a new variables instead of the one that I am trying to reproduce)
3. Which is faster in execution: Updating a variable through a) writing to property node/value or b) through local variable
Everyone’s input is welcomed, so if this question is already answered, please
feel free to add additional comments/answers!

1. Use Local Variables in user interface code and no where else. The only exception is using a local variable of a cluster output to define the datatype for a bundle by name node.
2. You can drag copy them then right click to get to a menu of all the currently defined controls and indicators on the VI.
3. B. The problem with A is that it forces a thread switch to the user interface thread--which can take time if you aren't already in it, and it's a very convoluted process under the hood. NI's advice never update indicator values through a property node unless you absolutely, positively can't figure out some other way of doing it.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

BIDS 2008 R2 freezes on large SSIS package when attempting to browse local variable

Hi,
When I set a break point on a control component within a large package and then attempt to watch local variables BIDS freezes. I then have to end BIDS using Task Manager.
So whilst debugging I view local variables the following way; -
When I try and expand the following variables tree BIDs freezes. The Task Manager on my desktop reports that my desktop where I am running BIDs is 80% idle.
Any help would be greatly appreciated.
Kind Regards,
Kieran.
Kieran Patrick Wood http://www.innovativebusinessintelligence.com http://uk.linkedin.com/in/kieranpatrickwood http://kieranwood.wordpress.com/

Hi Arthur,
Yes ... but if I am going to try and persuade my client to buy me a new laptop or upgrade my existing laptop to enable me to run BIDs against their servers I need to be more specific.
My current laptop has; -
Windows 7 Professional 64 Bit,
8 GB RAM,
Intel (R) Core (TM) i7-3630QM CPU @2.40Ghz
A Solid state drive with 80Gb free space.
To be honest it's the best laptop a client has ever loaned me. However the SSIS package which triggers the freeze is particularly large in terms of number of variables and size of control flow.
Whilst the freeze occurs as mentioned above the
Windows Task Manager reports; -
System Idle Process is set to 90+%
Memory usage set to 3.6Gb
Resource Monitor reports disk activity at virtually 0.
I wonder if there is an internal cap on resources within BIDs?
Any further help would be greatly appreciated.
Kind Regards,
Kieran.
Kieran Patrick Wood http://www.innovativebusinessintelligence.com http://uk.linkedin.com/in/kieranpatrickwood http://kieranwood.wordpress.com/

JDev903 debugger doesn't display local variable when debugging into JDK src

Hi,
I found that JDev903 debugger doesn't display local variables in the "smart data" and "data" panels when debugging into the JDK src. For most of the time, it only shows "this" object.
Is this right? How do I setup JDev903 to display local variables in debugger?
thanks,
Richard

Hi Fred,
Did you forget to put resultFormat="e4x"?

Unable to see local variable values when debugging java

Hi,
I am using JDev 10.1.2 with java version 1.4.2_04.
I have been using JDev to debug my java programs. But suddenly from this morning I am unable to see local variable values. I am able to see class and instance variables. This has happened to me before and I had restarted my machine couple of time, to get this sorted. But this time, nothing helps. Going thru the forum I found out that Include Debug information (Project Properties -> Compiler Option) need to be turned ON. It is already turned ON for me.
I would greatly appreciate if you could let me know how to crack this problem.
Thanks in advance.

No. The local variables 'used' to show up during debugging. But erratically it doesn't show up local variable values. I had to restart my machine couple of times whenever this happens, inorder to see the local variable values. But this time even restarting doesn't help.
Is there any preference setup that need to be turned on/off to see local variables?
Also I can't step into a static method now. Any idea why this happens?

Format of Variables Change When Debugging

When debugging in LabWindows, the format of the variables (decimal, hex, ASCII, etc.) is always set to the default under certain circumstances. For example if you step into a function, change format of a variable, step out then back in, the format has been reset to the default. There are other instances when you run, stop, rebuild and debug where this is done also.
I've asked NI to explain why the variable format can't be retained, at least within one debug session (until exiting LabWindows). The explanation is they use a stack-based system to store this information so it is lost during debug.
I find this to be an extreme annoyance and an enormous waste of time. For example, I deal with a lot of arrays of binary data. Seeing these array values in ASCII is of no value. So I'm nearly constantly setting the format back to hex during debugging.
I'm curious whether anyone else thinks this is a problem. NI knows about this, but it's unlikely they'll do anything unless there is a lot of feedback from us users on the value of fixing this. Post a note and let me (and NI) know what you think, whether you think this is important or not.
Thanks,
Dave

Hi Chris,
Yes, using Format >> Preferences is exactly what I was talking about when I said "change the format of a variable". Thanks for giving the exact details of doing this.
I'm still using v8.1. I'm leery of renewing my service contract because I don't feel NI is listening to me (as a customer, not just a LabWindows user) regarding the issues that affect my work and ways to greatly improve my productivity. I have been suggesting this for a few years now, to no avail, both with tech support on the phone and through your product suggestion center.
I can't explain all the intricacies of the issue. Maybe what you have to do is set breakpoints and run rather than step in and out. Here's what an engineer in NI's R&D center said:
It's not actually rebuilding the project that causes the information to be lost. It's actually even worse than that. As variables come in and out of scope, the formatting and the expand/collapse state of each variable is lost. So, if you've hit a breakpoint in a function and re-formatted a local variable, and then continue debugging outside the function, eventually stepping back into the function, the formatting for the original variable is reset when the item is created anew in the variable display, based on the data type of the variable.
The problem we have is that the formatting information is stored in stack-based memory which is associated with the actual items that you see in the variable display. As these items disappear and are re-created in the variable display, the formatting information is reset.
The complexity of representing variable scope information, including arbitrary block scopes, makes it pretty hard to maintain variable information in global, non-stack-based memory. It's obviously not impossible, but unfortunately it would require a fundamental redesign of our debugging paradigm.
Finally, we have heard this request from multiple customers, and I assure you that you are not the only customer who has asked for this feature. The problem with this feature, as with many other feature requests is one of trade-off. It is obviously impossible to accept all the feedback that we receive, and so we are constantly having to weigh development costs of a particular feature, the risks involved in implementing it, and how widespread its benefits are. So far, this feature has not made the cut. However, this does not mean that we're ignoring it, or any other customer feedback. Many customer-requested features have made it into previous releases, and we're confident that this will too, in the not too distant future. As a matter of fact, we can honestly say that most new features in a given CVI release originate with customer requests. I also just want to re-emphasize that each time you reiterate how important a given feature is, it drives up its priority and makes it more likely that we will implement it sooner, rather than later. With that in mind, we definitely welcome your suggestion to post a note about this request in the forum. We expect other people to second the request, and the more people that do that, the better.
So my question wasn't posted for NI to respond. It was to find out if anybody else using LabWindows finds this issue to be detrimental to productivity.
Thanks,
Dave

Empty variable pane when debugging

I'm fairly new to flex builder and very new with the
debugger. For some reason when I am debugging my application my
variables pane is coming up empty, no variables at all listed. Does
anyone have any idea what might cause this? My console is updating
working correctly. Its making life dificult as you may imagine.
Thanks
Adam

No. The local variables 'used' to show up during debugging. But erratically it doesn't show up local variable values. I had to restart my machine couple of times whenever this happens, inorder to see the local variable values. But this time even restarting doesn't help.
Is there any preference setup that need to be turned on/off to see local variables?
Also I can't step into a static method now. Any idea why this happens?

Can't see 'Local Variables' while debugging in Sun Studio 11

I am debugging a C/C++ application built with Sun Studio 11 running on Solaris 10. I load the application as always, set a breakpoint and run. The debugger stops at the assigned breakpoint as expected.
The issue is that at this point there are no local variables displayed in the local variables pane.
I have tried restarting SS11, rebuilding, etc...
This is the first time I have seen this happen.
Does anyone else have an idea what is wrong?

Does adding a particular variable to Watch view help? (it can be done by typing "display <variable>" in dbx command line).
You can also try erasing (or better moving to a temporary location) all Sun Studio settings like this:
mv -f ~/.sunstudio /tmpand start debugging session again.

Two unexpected Locals variables when iterating over array of containers.

Hi,
I iterate over an array of containers. In the ForEach loop step variables format I have defined two variables; one is current offset, second one is current element.
The loop works fine.
However, during the debug process, I've spotted two new Locals variables called __ElementSibling0 (type: number) and __ForEachReleaser0 (type: obj. reference) created silently by TS as soon as I start iterating over my array. What are they?
Do they exist because:
I'm iterating over an array of containers, or
I use the _currentElement_Freq variable, or
it always like that?
Solved!
Go to Solution.

Those are used by the implementation of the For Each step. You can see them only because you have enabled the Show Hidden Properties setting.
You can safely ignore their presence.

When debugging package, local variables always listed as 'null'

Similar Messages

Maybe you are looking for