[BTRACE-78] Ability to find values of local variables when reaching specific line number using @Location about btrace HOT 7 CLOSED

+1 for this feature : )

from btrace.

[author="j.bachorik", created="Fri, 11 May 2012 18:44:43 +0200"]

Probably could be achieved but it wouldn't work 100%. You would need the class data with debugging symbols in order to match the stack pointer to a local variable name.
Definitely not for 1.2.*

from btrace.

[author="grnch", created="Fri, 14 Mar 2014 14:06:02 +0100"]

Are there still any plans to implement this?

Please consider doing this, it would be an absolutely killer feature.

It would essentially complete the cycle and turn BTrace into a full fledged "programmable read-only debugger" for production instances. It would be indispensable for those weird bugs that you cannot reproduce on test servers, and if you just knew the value of that one local variable on the production server it would give you a clue what the problem is.

It would be fine if this feature only works with classes that have debug symbols, the probe can just fail if the class does not have debug info.

from btrace.

[author="grnch", created="Fri, 14 Mar 2014 14:07:02 +0100"]

Or as a fall back you could maybe provide all local variables in an AnyType[] array, similar to how method parameters are provided? After all, method parameters and local variables sit in the same array on the JVM stack frame.

That way even without the names of local variables you could at least guess which slot in the array corresponds to which local var, with a little experimentation.

But this is less important, even a simpler implementation that just fails when there is no debug info would be great.

from btrace.

I'm looking for this feature, then see this issue. I wish it will come soon.

from btrace.

this's a great feature.hope come soon.

from btrace.

Stale issue message

from btrace.