0

I am using the Flex Builder 3 debugger almost every day and it's starting to be a real pain that the 'Variables' tab in the 'Flex Debugging' view doesn't show local variables, only 'this' is displayed.

Also I can not add Watch Expressions for local variables.

Am I forgetting something here or is the debugger just very limited?

Thanks

Bill the Lizard
  • 398,270
  • 210
  • 566
  • 880
motto
  • 1,305
  • 3
  • 16
  • 30
  • 1
    I just double-checked, but I've got no problems viewing local variables in my flex debugger. Unfortunately I don't have a clue what might be causing your debugger to not show them. – Simon Groenewolt Feb 11 '10 at 23:19
  • 1
    Sounds like it might be time to reinstall Flex Builder. I've never had this problem happen and been developing with Flex for 4+ years. – cliff.meyers Feb 13 '10 at 18:00
  • I used to be able to see private local variables without any problems but that capability is gone. I can only see public variables. The hover still works for me. I too, have been hitting the Out of Memory errors. In fact, it was around the time the memory errors started that I noticed private vars not showing in the debugger. Has re-installing worked for anyone? – Suzanne Mar 15 '11 at 16:43

3 Answers3

1

To see if Flex Builder is even tracking your local variables properly, set a breakpoint somewhere in a function. Once you hit that breakpoint, you can also "hover" over a variable in your source code, and a tooltip should show the current value of that variable.

bugsmash
  • 33
  • 1
  • 7
1

I have the same problem that motto described. Local variables are not displayed when debugging, "hover" method doesn't work either. You can always use trace() or Loging API. The problem occurred to me yesterday and the only thing I noticed is that the project stopped to compile using ant script due to OutOfMemoryError (I usually build project using FB, but sometimes FlexBuilder doesn't show errors/warnings and compiling via ant script is the only way I know to find them).

Garlik
  • 120
  • 7
  • The issue is quite funny because FB doesn't display local variables in one function and in another it does. – Garlik Apr 07 '10 at 12:03
1

Sometimes, FB has problems if the current function is further down in a larger file. Moving the function code up solves the problem (but exposes the same for another funciton further doen then). It seems that FB can only gather a certain amount of metadata for the currently open file.

Peter Painter
  • 11
  • 1