[lldb-dev] [Bug 27182] New: TestCallWithTimeout.py failing on OS X

2016-04-01 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27182 Bug ID: 27182 Summary: TestCallWithTimeout.py failing on OS X Product: lldb Version: unspecified Hardware: PC OS: MacOS X Status: NEW Severity: normal

Re: [lldb-dev] Review of API and remote packets

2016-04-01 Thread Greg Clayton via lldb-dev
We also need to think about all other types of tracing. It might make more sense to keep these calls on SBProcess and have the calls simply be: lldb::SBTrace lldb::SBProcess::StartTrace(SBTraceOptions &trace_options, lldb::SBError &error); And you would need to specify which threads in the SBT

[lldb-dev] ReadCStringFromMemory deprecated? (API)

2016-04-01 Thread Paul Peet via lldb-dev
Hey, I noticed that SBProcess::ReadCStringFromMemory uses the deprecated Process::ReadCStringFromMemory function. The note says that it was deprecated in favor of ReadStringFromMemory. Is it possible to add that function to the SBProcess api ? ___ lldb-d

[lldb-dev] [Bug 27181] Xcode gtests: ensure they run, not just build, on Xcode target

2016-04-01 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27181 Todd Fiala changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|lldb-dev@lists.llvm.or

[lldb-dev] [Bug 27181] New: Xcode gtests: ensure they run, not just build, on Xcode target

2016-04-01 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27181 Bug ID: 27181 Summary: Xcode gtests: ensure they run, not just build, on Xcode target Product: lldb Version: unspecified Hardware: PC OS: MacOS X Statu

[lldb-dev] [Bug 27180] New: test infra: OS X Green Dragon - switch to run tests with just-built clang

2016-04-01 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27180 Bug ID: 27180 Summary: test infra: OS X Green Dragon - switch to run tests with just-built clang Product: lldb Version: unspecified Hardware: PC OS: All

[lldb-dev] [Bug 27180] test infra: OS X Green Dragon - switch to run tests with just-built clang

2016-04-01 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27180 Todd Fiala changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|lldb-dev@lists.llvm.or

[lldb-dev] [Bug 27179] test infra: Green Dragon OS X builder is sometimes accessing an unguarded missing dictionary key, xUnit formatter

2016-04-01 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27179 Todd Fiala changed: What|Removed |Added Assignee|lldb-dev@lists.llvm.org |todd.fi...@gmail.com -- You are receiving this ma

[lldb-dev] [Bug 27179] New: test infra: Green Dragon OS X builder is sometimes accessing an unguarded missing dictionary key, xUnit formatter

2016-04-01 Thread via lldb-dev
https://llvm.org/bugs/show_bug.cgi?id=27179 Bug ID: 27179 Summary: test infra: Green Dragon OS X builder is sometimes accessing an unguarded missing dictionary key, xUnit formatter Product: lldb Version: unspecifi

Re: [lldb-dev] SBProcess::Detach kills target

2016-04-01 Thread Pavel Labath via lldb-dev
> It might be also possible to run an expression that will route > stdin/stdout/stderr to /dev/null before detaching if we know that we have a > master/slave pty hooked up the the inferior's in/out/err. We could run an > expression like: (At least on linux) you would also need something like: io

Re: [lldb-dev] Review of API and remote packets

2016-04-01 Thread Pavel Labath via lldb-dev
I second Greg's suggestions, and I have some thoughts of my own: - with the proposed API, it is not possible to get a trace for newly created threads - the process needs to be stopped first, so you can enable trace collection. There certainly are cases where this could be problematic, e.g. if you