What are you trying to achieve?
Live variables in Embitz are possible because the whole chain EBlink - GDB - EmBitz is optimized for this. I have modified GDB and wrote EBlink because of live variables and wrote the Embitz debugger plugin to make full use of live variables. I introduced debugger plugin plugins like OSview and a upcoming debugger plugin HeapView with realtime heap visualisation about allocation and fragmentation.
If you want to use EBlink standalone in your test workflow then it is only possible on address level. But you could write an ELF parser to get address location from the debug info.
Live variables in Embitz are possible because the whole chain EBlink - GDB - EmBitz is optimized for this. I have modified GDB and wrote EBlink because of live variables and wrote the Embitz debugger plugin to make full use of live variables. I introduced debugger plugin plugins like OSview and a upcoming debugger plugin HeapView with realtime heap visualisation about allocation and fragmentation.
If you want to use EBlink standalone in your test workflow then it is only possible on address level. But you could write an ELF parser to get address location from the debug info.