Issues with frame variable when examining std::vector

[jkunlin]

Command 'frame variable' (so as the locals buffer) always shows that 'size = 0', while it works well with command 'display vec'.

I test with the run.sh, and here is the report:

Note: :LL- commands are not bound with this test instance
error: libc.so.6 0x003de11b: DW_TAG_variable has an invalid location:
DW_OP_lit13
DW_OP_const8s(0x0000000000000000)

[jkunlin]

"display" dose not print any message in log buffer as well.

BTW, everything goes well when using terminal.

[critiqjo]

Command 'frame variable' (so as the locals buffer) always shows that 'size = 0', while it works well with command 'display vec'.

Yes, I'm aware of this bug. But this does not have anything to do with this plugin. This is a bug in their Python API. I'm not really sure why, but there are many breakages when working from the Python API which works perfectly with the lldb tool (another example is remote debugging).

"display" dose not print any message in log buffer as well.

display command is, I believe, well-tied with the front-end. So in order to get it work in this plugin, significant work may have to be done. (I am unable to recall much details about this, so I might be wrong.)

I'll leave this issue open until a "Known Issues" section is added to README.

[jkunlin]

Is there any way to make "frame variable" works correctly?

[critiqjo]

@jkunlin It might work in remote debugging mode. Start the server using lldb-server p --server --listen 2345 so that the server doesn't exit when the client leaves. (Note: For security reasons, it might be good to use a firewall to block remote connections to that port, at least while using the --server switch.)

[jkunlin]

It doesn't works in remote debugging mode too.

[johncf]

cc #59