Log Analyzer code stepping jumps to VisualForce page code instead of Controller code

[Dave Seligson]

If I'm using Log Analyzer to step thru the logs of a VF Page, the code jumps to the corresponding line number in the Visualforce Page and *not* that of the Controller.  This means I have to continually switch to the window with the controller and scroll to the new line.

[Scott Wells]

Dave, I'm unable to reproduce this. I just tried it with a few of my VF pages and even their remote actions, and in all cases the debugger ended up stepping through the correct lines in the associated controller code. Any chance you could put together a really simple standalone page/controller that reproduces this consistently and provide that?

[Scott Wells]

Issue tracker grooming. If this is still an issue, please feel free to reopen, ideally with a concrete reproduction scenario.