[lldb-dev] [Bug 20406] Can't build lldb 3.4.2 on OS X 10.8.5

https://llvm.org/bugs/show_bug.cgi?id=20406 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

[lldb-dev] [Bug 16172] Continue after process interrupt does not work correctly

https://llvm.org/bugs/show_bug.cgi?id=16172 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

[lldb-dev] [Bug 15039] lldb.SBProcess.GetSTDOUT() returns empty string instead of inferior output

https://llvm.org/bugs/show_bug.cgi?id=15039 lab...@google.com changed: What|Removed |Added Status|REOPENED|RESOLVED CC|

[lldb-dev] [Bug 24976] Data from SBProcess::PutSTDIN appears in SBProcess::GetSTDOUT

https://llvm.org/bugs/show_bug.cgi?id=24976 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[lldb-dev] [Bug 15989] Unable to allocate memory after inferior crash and step

https://llvm.org/bugs/show_bug.cgi?id=15989 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

[lldb-dev] [Bug 17237] Automated tests are missing for ELF core file support

https://llvm.org/bugs/show_bug.cgi?id=17237 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

[lldb-dev] [Bug 22252] llgs tests should not write their log files in-tree

https://llvm.org/bugs/show_bug.cgi?id=22252 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

[lldb-dev] [Bug 27652] Tests with syntax errors don't get flagged as erroneous

https://llvm.org/bugs/show_bug.cgi?id=27652 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[lldb-dev] [Bug 28041] New: Tab completion adds backslashes to function names, which causes them not to match

https://llvm.org/bugs/show_bug.cgi?id=28041 Bug ID: 28041 Summary: Tab completion adds backslashes to function names, which causes them not to match Product: lldb Version: 3.6 Hardware: Macintosh OS: MacOS

Re: [lldb-dev] Structure variable names

Thanks Greg and Duane, I will try these things and comeback if I have further questions. -Jiten > On Jun 7, 2016, at 12:28 PM, du...@duaneellis.com wrote: > > You need to understand the DWARF (debug info) > > Try this: > > Create a *SIMPLE* C file - with a simple structure > Do *not*

Re: [lldb-dev] [cfe-dev] [llvm-dev] GitHub anyone?

On Jun 6, 2016, at 10:07 AM, James Y Knight via cfe-dev wrote: > +1 to that. I would strongly suggest that we continue to commit to master > first, like we've always done in llvm. > More generally, I suggest that we keep a discussion about moving hosting and svn->git

Re: [lldb-dev] Structure variable names

You need to understand the DWARF (debug info)Try this:Create a *SIMPLE* C file - with a simple structureDo *not* "#include" any file - make your file 100% standalone.(later you can get more complicated, you want a simple translation unit)Do the following with both GCC and LLVMCompile this file

Re: [lldb-dev] Structure variable names

> On Jun 7, 2016, at 9:56 AM, Jiten Thakkar via lldb-dev > wrote: > > Hi All, > I am working on a project as part of my graduate study which uses LLVM. > I am new to LLVM and lldb to be particular. > My goal is to get names of the parameters to functions. If the

[lldb-dev] Structure variable names

Hi All, I am working on a project as part of my graduate study which uses LLVM. I am new to LLVM and lldb to be particular. My goal is to get names of the parameters to functions. If the parameter is a variable in a structure, it is represented as an offset in the structure. I want to get the

Re: [lldb-dev] Release_38 cherry-picks

All of those look simple enough. Two are for testing only and the last one is a simple fix needed for PIE exe debugging. Greg Clayton > On Jun 6, 2016, at 4:22 PM, Francis Ricci via lldb-dev > wrote: > > Hi all, > > I'd like to merge a few more small bugfixes onto

Re: [lldb-dev] Catching async debugger output

No there is no way as this is async output that isn't tagged to any specific command. My suggestion is to not use command line stop hooks and catch the stops in your python and do the stuff that you were doing with stop hooks by using the python API. Greg > On Jun 6, 2016, at 7:05 PM, Vadim

Re: [lldb-dev] Release_38 cherry-picks

Hi, You should get approval from the release manager (Tom Stellard) first. > -Original Message- > From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Francis > Ricci via lldb-dev > Sent: 07 June 2016 00:23 > To: LLDB > Subject: [lldb-dev] Release_38 cherry-picks > > Hi