[lldb-dev] lldb fails to examine any variable with the message - Interpreting the expression locally failed: Interpreter couldn't write to memory
Samuel Jacob
samueldotj at gmail.com
Wed Apr 17 20:52:30 PDT 2013
Hi Dan,
Can you please check this?
Thanks
Samuel
On Wed, Apr 17, 2013 at 4:21 PM, Samuel Jacob <samueldotj at gmail.com> wrote:
> lldb build from trunk running on Ubuntu 12.04 is not able examine any variable.
>
> $cat test1.c
> int main(int argc, char argv[])
> {
> char *crash=0;
>
> *crash = 0;
> return 0;
> }
>
> $gcc -O0 -g3 ./test1.c
>
> $lldb ~/a.out
> Current executable set to '/mts/home3/jacobs/a.out' (x86_64).
>
> (lldb) run
> Process 16615 launched: '/mts/home3/jacobs/a.out' (x86_64)
> Process 16615 stopped
> * thread #1: tid = 0x40e7, 0x00000000004004cb a.out`main(argc=1,
> argv=0x00007fff336ad2a8) + 23 at test1.c:5, stop reason = invalid
> address
> frame #0: 0x00000000004004cb a.out`main(argc=1,
> argv=0x00007fff336ad2a8) + 23 at test1.c:5
> 2 {
> 3 char *crash=0;
> 4
> -> 5 *crash = 0;
> 6 return 0;
> 7 }
> (lldb) p argc
> error: Interpreting the expression locally failed: Interpreter
> couldn't write to memory
>
> But before crashing If a breakpoint was setup, lldb stops at the
> breakpoint and works fine.
>
> Is it a known issue or should a file a bug report?
>
> Samuel
More information about the lldb-dev
mailing list