[lldb-dev] [Bug 24915] Unsupported immediate operand assembler branch mnemonics

https://llvm.org/bugs/show_bug.cgi?id=24915 ema...@freebsd.org changed: What|Removed |Added Component|All Bugs|new bugs Version|unspecified

[lldb-dev] [Bug 24916] New: Expression evaluation: out-of-line definition of '$__lldb_expr' does not match any declaration in 'Foo'

https://llvm.org/bugs/show_bug.cgi?id=24916 Bug ID: 24916 Summary: Expression evaluation: out-of-line definition of '$__lldb_expr' does not match any declaration in 'Foo' Product: lldb Version: unspecified Hardware: PC

Re: [lldb-dev] I see at least one test hanging...

I am experiencing a similar issue with the 3.7 branch on all Ubuntu version: https://llvm.org/bugs/show_bug.cgi?id=24912 Debian works fine. Does it ring a bell? Sylvestre Le 22/09/2015 18:01, Todd Fiala via lldb-dev a écrit : > Hey all, > > On the Linux build bot, I'm seeing at least one test

[lldb-dev] [Bug 24912] New: lldb-test-traces freeze on all Ubuntu

https://llvm.org/bugs/show_bug.cgi?id=24912 Bug ID: 24912 Summary: lldb-test-traces freeze on all Ubuntu Product: lldb Version: 3.7 Hardware: PC OS: Linux Status: NEW Severity: normal Priority:

[lldb-dev] Moving test runner timeout logic into Python

Hi all, Over the last two days, I've hit some inconsistencies across platforms surrounding signal handling and the operation of the timeout/gtimeout executable mechanism that we use to handle timeouts of tests. The net result is I still see tests sometimes hang up the test running process, even

Re: [lldb-dev] Moving test runner timeout logic into Python

We definitely want timeouts. I was planning to implement timeout / gtimeout in C++ and checking it in and building it as part of the build process. But this would be better for obvious reasons. On Wed, Sep 23, 2015 at 2:56 PM Todd Fiala wrote: > Yeah good idea. > >

Re: [lldb-dev] Moving test runner timeout logic into Python

Cool. Win win :-) On Wed, Sep 23, 2015 at 2:57 PM, Zachary Turner wrote: > We definitely want timeouts. I was planning to implement timeout / > gtimeout in C++ and checking it in and building it as part of the build > process. But this would be better for obvious reasons.

Re: [lldb-dev] Moving test runner timeout logic into Python

Can you offer a hint about how you plan to implement this? When you say it we should get the same behavior everywhere, I assume this means Windows too, which currently does not support running with a timeout at all (because timeout / gtimeout aren't present) On Wed, Sep 23, 2015 at 2:22 PM Todd

Re: [lldb-dev] Moving test runner timeout logic into Python

Yep - the approach (for now) is likely to look like: p = subprocess.Popen(...) # exact call differs between Windows/Non-Windows done_event = # some kind of semaphore/event, probably threading.Thread.Event() spinup thread 1, running this code: # Thread 1 - grab output, do communicate() call

Re: [lldb-dev] Moving test runner timeout logic into Python

No obvious reason I see why that wouldn't work. You probably want to wrap the "thread 1" code in a try: ... except: pass because p.terminate probably will cause an exception on the other thread. On Wed, Sep 23, 2015 at 2:40 PM Todd Fiala wrote: > A nice bit here, also, is