[lldb-dev] [Bug 24388] lldb cannot launch process on Android mips/mips64 target

[via lldb-dev]

https://llvm.org/bugs/show_bug.cgi?id=24388

Bhushan Attarde  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||bhushan.atta...@imgtec.com
 Resolution|--- |WORKSFORME

--- Comment #4 from Bhushan Attarde  ---
Feel free to re-open if you still have this problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 27634] Spelling fixes for lldb

[via lldb-dev]

https://llvm.org/bugs/show_bug.cgi?id=27634

ema...@freebsd.org changed:

   What|Removed |Added

 CC||ema...@freebsd.org
   Assignee|lldb-dev@lists.llvm.org |ema...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Closing TTY window while in a break state using LLDB-MI does not stop debugging

[Pierson Lee (PIE) via lldb-dev]

Hi,

Running into a problem where closing the TTY window on OS X while on a 
breakpoint using LLDB-MI does not allow the SIGHUP to be passed through to the 
debuggee. I had to add the following call to get the debuggee to terminate when 
closing the window if LLDB-MI was not in a break state.

process handle --pass true --stop false --notify false SIGHUP

Looking for some help on where to look to find out what is wrong. I've been 
looking in debugserver.cpp thinking it would be in HandleProcessStateChange but 
I haven't seen a call to it when I close the window. Also looking to see where 
the signal handler might be because debugserver.cpp's signal_handler method is 
also not called.

Thanks
Pierson
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 28621] New: lldb-mi can't get variables of a frame (-stack-list-* MI-commands) if the thread didn't cause the stop event

[via lldb-dev]

https://llvm.org/bugs/show_bug.cgi?id=28621

Bug ID: 28621
   Summary: lldb-mi can't get variables of a frame (-stack-list-*
MI-commands) if the thread didn't cause the stop event
   Product: lldb
   Version: 3.9
  Hardware: Macintosh
OS: MacOS X
Status: NEW
  Severity: normal
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: edmu...@microsoft.com
CC: llvm-b...@lists.llvm.org
Classification: Unclassified

Created attachment 16771
  --> https://llvm.org/bugs/attachment.cgi?id=16771&action=edit
Simple repro

lldb-mi provides a set of commands to list variables from a stack frame,
namely: stack-list-variables -stack-list-arguments and -stack-list-locals.

In a multithreaded process, these commands return a empty list if queried for a
thread that didn't cause the stopped event.

The root cause for this bug is https://llvm.org/bugs/show_bug.cgi?id=15824

lldb-mi checks the stopped reason for the thread being queried through those
commands and returns an empty list if the stopped reason in none or invalid.

This doesn't affect the normal command line interface for lldb (through the
similar command "frame variable") since lldb doesn't have such a strict check
(it just checks that the process is paused and that the frame exists).

In order to fix this bug, lldb-mi should perform the same checks as lldb.

Repro steps:

1. Compile the attached file a.cpp: clang++ -g a.cpp -lpthread
2. Start lldb-mi and execute the following

-file-exec-and-symbols ""
-break-insert -f on a.cpp:5
-exec-run

After hitting the breakpoint
-stack-list-variables 0 --thread 1 --frame 5
^done,variables=[]

However, going through the non-MI command:

-interpreter-exec console "thread select 1"
-interpreter-exec console "frame select 5"
-interpreter-exec console "frame variable"
(int) argc = 1
(char **) argv = 0x7fff5fbffee0
(int) x = 3
(int) y = 0
(pthread_t) id = 0x0001000b6000

The expected result is:
-stack-list-variables 0 --thread 1 --frame 5
^done,variables=[{arg="1",name="argc"},{arg="1",name="argv"},{name="x"},{name="y"},{name="id"}]

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev