Re: [lldb-dev] settings set target.source-map question

2018-03-14 Thread Pavel Labath via lldb-dev
Sounds like a good idea to me. (For testing I'd recommend a .ll file with the paths you need hard coded and lldb-test breakpoint.) On Wed, 14 Mar 2018 at 05:16, Greg Clayton via lldb-dev < lldb-dev@lists.llvm.org> wrote: > When using "settings set target.source-map", when we try to set >

Re: [lldb-dev] increase timeout for tests?

2018-03-14 Thread Pavel Labath via lldb-dev
+1 On deleting the lldb-mi tests and increasing the timeout. On Wed, 14 Mar 2018 at 02:27, Jim Ingham wrote: > It is unfortunate that we have to set really long test timeouts because we > are timing the total Test class run, not the individual tests. It is > really

[lldb-dev] Converting a pointer to python string in a formatter

2018-03-14 Thread Florin Trofin via lldb-dev
Hi, I came across the formatter example in unicode_strings.py where in utf16_summary() I see this code: string_data = value.process.ReadMemory(pointer, length, error) # utf8 is safe to emit as-is on OSX return '"%s"' % (string_data.decode('utf-16').encode('utf-8')) I am trying to replicate that

[lldb-dev] [Bug 36740] New: Fix tests which check the lldb-mi -gdb-set and -gdb-show commands

2018-03-14 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=36740 Bug ID: 36740 Summary: Fix tests which check the lldb-mi -gdb-set and -gdb-show commands Product: lldb Version: unspecified Hardware: PC OS: All

[lldb-dev] [Bug 36739] New: Fix tests which check that the lldb-mi driver exits properly

2018-03-14 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=36739 Bug ID: 36739 Summary: Fix tests which check that the lldb-mi driver exits properly Product: lldb Version: unspecified Hardware: PC OS: All Status:

[lldb-dev] [Bug 36741] New: Fix tests which check the lldb-mi -symbol-xxx commands

2018-03-14 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=36741 Bug ID: 36741 Summary: Fix tests which check the lldb-mi -symbol-xxx commands Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity:

Re: [lldb-dev] increase timeout for tests?

2018-03-14 Thread Ted Woodward via lldb-dev
I don't see 22 lldb-mi tests xfailed everywhere. I see a lot of tests skipped, but those are clearly marked as skip on Windows, FreeBSD, Darwin, Linux. I've got a good chunk of the lldb-mi tests running on Hexagon. I don’t want them deleted, since I use them. lldb-mi tests can be hard to debug,

Re: [lldb-dev] increase timeout for tests?

2018-03-14 Thread Vedant Kumar via lldb-dev
I got the 22 number from a command which may have counted too much: find . -name \*TestMi\*.py -exec grep -E "(unittest2\.)?expectedFailure(All)?" {} \; | wc -l Some of the 'expectedFailureAll' decorators actually specified an OS list. I'm not planning on touching those. There were a handful

[lldb-dev] [Bug 36746] New: Allow 'quit' to take an exit code

2018-03-14 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=36746 Bug ID: 36746 Summary: Allow 'quit' to take an exit code Product: lldb Version: 6.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P