Re: [lldb-dev] queue-name parameter

[Fernando Bunn via lldb-dev]

Jim,
you're right, I was getting a false positive with -Q, sorry for the
confusion.

So it seems I'm having 2 issues on Xcode, right?
A - No rejection of illegal options (-Q)
B - "-q" with the correct queue name is not working.

Here's what I'm doing for B:

*1 - (lldb) thread info*
thread #1: tid = 0xfc5f, 0x0001070418f4
ThreadTest`ViewController.viewDidLoad(self=0x7f940610d270) at
ViewController.swift:16:9, queue = 'com.apple.main-thread', stop reason =
breakpoint 1.1

*2 - (lldb) breakpoint set --file ViewController.swift --line 26 -q
com.apple.main-thread*
Breakpoint 2: where = ThreadTest`ThreadTest.ViewController.viewDidLoad() ->
() + 942 at ViewController.swift:26:15, address = 0x000107041c0e

*3 - (lldb) breakpoint list 2*
2: file = 'ViewController.swift', line = 26, exact_match = 0, locations =
1, resolved = 1, hit count = 0 Options: enabled queue name:
"com.apple.main-thread"
  2.1: where = ThreadTest`ThreadTest.ViewController.viewDidLoad() -> () +
942 at ViewController.swift:26:15, address = 0x000107041c0e, resolved,
hit count = 0

On #1 I just make sure the queue name is correct, com.apple.main-thread,
then on #2 I set the breakpoint with "-q", and on #3 I make sure that the
parameter was set correctly, and I do see the *enabled queue name:
"com.apple.main-thread" *in there, but the breakpoint is never executed.

But if I set * breakpoint set --file ViewController.swift --line 26*,
without -q, the breakpoint is executed normally.
And to check that the queue name is "com.apple.main-thread" when this
breakpoint is executed I did the following:

*1 - (lldb) breakpoint set --file ViewController.swift --line 26*
Breakpoint 3: where = ThreadTest`ThreadTest.ViewController.viewDidLoad() ->
() + 942 at ViewController.swift:26:15, address = 0x000104a01c0e
*2 - (lldb) c*
Process 1242 resuming
*3 - (lldb) thread info*
thread #1: tid = 0x11cd2, 0x000104a01c0e
ThreadTest`ViewController.viewDidLoad(self=0x7fcb15d09d50) at
ViewController.swift:26:15, queue = 'com.apple.main-thread', stop reason =
breakpoint 3.1

I can verify that on #3 the queue name is in fact com.apple.main-thread but
if I add -q *com.apple.main-thread, *it doesn't work.

At this point, I'm not sure what to do next, maybe file a radar with Apple?
Thanks for your help, I really appreciate it :)

--
Fernando



On Fri, Jul 19, 2019 at 1:27 AM Jim Ingham  wrote:

> Fernando, I don't see quite what you do.  For me, -Q never sets the
> queue.  Rather, the current Xcode version of lldb seems to have a bug where
> it doesn't reject illegal options, so the -Q argument is silently
> discarded.  That would cause the breakpoint to "work" but it won't only
> stop on one queue. So I see:
>
>
> (lldb) break set -f main.c -l 10 -q whatever
> Breakpoint 1: where = SomeTool`main + 22 at main.c:13:3, address =
> 0x00010f66
> (lldb) break list 1
> 1: file = 'main.c', line = 10, exact_match = 0, locations = 1, resolved =
> 1, hit count = 0 Options: enabled queue name: "whatever"
>   1.1: where = SomeTool`main + 22 at main.c:13:3, address =
> 0x00010f66, resolved, hit count = 0
>
> That's right, it got the queue name and should match against it.  But:
>
> (lldb) break set -f main.c -l 10 -Q whatever
> Breakpoint 2: where = SomeTool`main + 22 at main.c:13:3, address =
> 0x00010f66
> (lldb) break list 2
> 2: file = 'main.c', line = 10, exact_match = 0, locations = 1, resolved =
> 1, hit count = 0
>   2.1: where = SomeTool`main + 22 at main.c:13:3, address =
> 0x00010f66, resolved, hit count = 0
>
> That one didn't get a queue name at all.  So it will always stop, but OTOH
> that's not really what you wanted.
>
> It sounds like what is really going on is that the queue matching isn't
> working as you expected, so when you actually DID set a queue name - using
> the "-q" option, the breakpoint wasn't stopping, but when you didn't set a
> queue name (with the bogus -Q option) it did stop.  So there might be
> something going wrong with the queue name matching?
>
> Note, this bug doesn't exist in current llvm TOT.  If you try with that
> lldb:
>
> (lldb) break set -f foo.c -l 10 -Q foo
> error: unknown or ambiguous option
>
> That's right, there is no -Q option...
>
> I'm surprised we have no tests for rejecting illegal options in the
> command interpreter, but I couldn't find any...
>
> Jim
>
>
>
> > On Jul 18, 2019, at 4:23 PM, Fernando Bunn via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> >
> > Hi, everyone.
> > I'm seeing an issue when using the -q parameter on a breakpoint using
> Xcode.
> >
> > when I run:
> > (lldb) help breakpoint modify
> > I see this:
> >
> >-q  ( --queue-name  )
> > The breakpoint stops only for threads in the queue whose
> name is
> > given by this argument.
> >
> > So far, so good.
> > Then I try to set a breakpoint with -q on it like so:
> > (lldb) breakpoint set --file ViewController.swift --line 27 -q
> com.apple.main-thread
> >
> > This doesn'

[lldb-dev] Cannot use system debugserver for testing

[Gábor Márton via lldb-dev]

Hi Stefan,

Since the commit
"[CMake] Always build debugserver on Darwin and allow tests to use the
system's one"
I cannot use the system debugserver for testing.
I receive the following error message from lldb when I execute "ninja
check-lldb":
```
runCmd: run
runCmd failed!
error: process exited with status -1 (Error 1)
```

I do set up "-DLLDB_USE_SYSTEM_DEBUGSERVER=ON" with cmake so I see
```
-- LLDB tests use out-of-tree debugserver:
/Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Resources/debugserver
```

Also, I have inspected the following test output
```
Command invoked: /usr/bin/python
/Users/egbomrt/llvm2/git/llvm/tools/lldb/test/dotest.py -q --arch=x86_64 -s
/Users/egbomrt/llvm2/build/release_assert/lldb-test-traces --build-dir
/Users/egbomrt/llvm2/build/release_assert/lldb-test-build.noindex -S nm -u
CXXFLAGS -u CFLAGS --executable
/Users/egbomrt/llvm2/build/release_assert/./bin/lldb --dsymutil
/Users/egbomrt/llvm2/build/release_assert/./bin/dsymutil --filecheck
/Users/egbomrt/llvm2/build/release_assert/./bin/FileCheck -C
/Users/egbomrt/llvm2/build/release_assert/bin/clang --codesign-identity -
--out-of-tree-debugserver --arch x86_64 -t --env TERM=vt100 -p
TestCModules.py --results-port 49931 -S nm --inferior -p TestCModules.py
/Users/egbomrt/llvm2/git/llvm/tools/lldb/packages/Python/lldbsuite/test/lang/c/modules
--event-add-entries worker_index=0:int
  1 out of 736 test suites processed - TestCModules.py
```
so it seems like the argument for --out-of-tree-debugserver is missing...

Could you please advise?

Thank you,
Gabor
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
We removed lldb-mi

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

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

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
We removed lldb-mi

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

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

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |INVALID
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
We removed lldb-mi

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

[lldb-dev] [Bug 22411] lldb-mi fails on FreeBSD due to apparent thread race conditions

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED
 Resolution|--- |INVALID

--- Comment #5 from Jonas Devlieghere  ---
We removed lldb-mi

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

[lldb-dev] [Bug 22841] lldb-mi tests fail on all Linux buildbots

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
We removed lldb-mi

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

[lldb-dev] [Bug 23494] lldb-mi binary causes "Do you want the application "lldb-mi" to accept incoming network connections?"

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com
 Resolution|--- |INVALID

--- Comment #3 from Jonas Devlieghere  ---
We removed lldb-mi

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

[lldb-dev] [Bug 24452] Get lldb-mi tests working on Windows

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
We removed lldb-mi

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

[lldb-dev] [Bug 17477] lldb doesn't report line number for NULL function pointer crash

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com
 Resolution|--- |WORKSFORME

--- Comment #1 from Jonas Devlieghere  ---
(lldb) r
Process 12820 launched: '/tmp/a.out' (x86_64)
Process 12820 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x0)
frame #0: 0x
error: memory read failed for 0x0
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x0)
  * frame #0: 0x
frame #1: 0x00010faa a.out`main at main.cpp:10:5
frame #2: 0x7fff70342c49 libdyld.dylib`start + 1
frame #3: 0x7fff70342c49 libdyld.dylib`start + 1

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

[lldb-dev] [Bug 26759] TestGoroutines.py failing on OS X

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
Go support was removed a while ago. This is no longer relevant.

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

[lldb-dev] [Bug 33643] TestGoAstContext fails with go 1.8

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
Go support was removed a while ago, this is no longer relevant.

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

[lldb-dev] [Bug 24895] test and assertion failures from Go support on FreeBSD

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #4 from Jonas Devlieghere  ---
Go support was removed a while ago. This is no longer relevant.

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

[lldb-dev] [Bug 27782] Go tests failing on OS X

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
Go support was removed a while ago. This is no longer relevant.

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

Re: [lldb-dev] [RFC] Removing lldb-mi

[Ted Woodward via lldb-dev]

As of yesterday, lldb-mi has been removed from lldb and moved to 
https://github.com/lldb-tools/lldb-mi .

Some questions:

  *   Is the expected way to build lldb-mi to drop the lldb-tools/lldb-mi repo 
into /tools/lldb-mi?
  *   The lldb-mi tests weren’t moved into the new repo on github. Do we plan 
on moving them?
  *   If we don’t move them, do we just rely on the lldb-mi executable not 
existing to keep from trying to run them?
  *   If we do move them, how do we run them?

Ted

From: lldb-dev  On Behalf Of Jonas Devlieghere 
via lldb-dev
Sent: Friday, July 5, 2019 11:44 AM
To: Raphael “Teemperor” Isemann 
Cc: LLDB 
Subject: [EXT] Re: [lldb-dev] [RFC] Removing lldb-mi

Thank you for doing this, Raphael. I believe this shows that it's possible to 
keep lldb-mi alive, without today's maintenance burden on the LLDB community, a 
solution that seems to appease everyones concerns in this thread. I hope this 
sparks interest for somebody to step up as a maintainer.

I went ahead and created a diff to add the proposed deprecations to the LLVM 
release notes: https://reviews.llvm.org/D64254
I'll put up another diff to remove the code, which we can land once LLVM 9 has 
branched.

Thank you,
Jonas

On Thu, Jul 4, 2019 at 12:24 PM Raphael “Teemperor” Isemann via lldb-dev 
mailto:lldb-dev@lists.llvm.org>> wrote:
I just went forward with this and made a quick test repo with an out-of-tree 
lldb-mi that compiles against the system LLDB: 
https://github.com/Teemperor/lldb-mi This seems to work fine with the exception 
of the python tests which require LLDB’s python code for testing which isn’t 
installed alongside LLDB. I guess we will have to see if we copy the related 
test code there or we just rewrite the test suite (which is anyway broken). On 
the upside, we can now just use Travis for CI as we don’t have to compile 
LLVM/Clang/LLDB, so that’s nice.

I’m in favor of deprecating lldb-mi with 9.0.0 and then we can give downstream 
time until 10.0.0 (or X.0.0 :) ) to package out-of-tree lldb-mi for users. 
Given how simple lldb-mi is, this seems like a reasonable timeframe.

- Raphael


On Jul 4, 2019, at 9:51 AM, Davide Italiano via lldb-dev 
mailto:lldb-dev@lists.llvm.org>> wrote:



On Thu, Jul 4, 2019 at 12:58 AM Zdenek Prikryl via lldb-dev 
mailto:lldb-dev@lists.llvm.org>> wrote:

We're using it with Eclipse and Eclipse based product, so I'd like to keep as 
well! :-)...

Zdenek

I do understand that there's desire from people to keep this around (from an 
user perspective), but I guess this fundamentally misses Jonas' original mail 
point.
lldb-mi has been unmaintained for a long time (at least the past two years from 
what I can tell), and we tried to use it in emacs without success.
It has never been a priority for many of the parties putting effort in lldb and 
I'm under the impression the situation won't change in the foreseeable future.
Unless somebody steps up as maintainer I don't think there's a lot of future 
for the tool.
Maybe a good compromise would be that of having lldb-mi living in a separate 
repo somewhere on GitHub, as it only uses the SBAPI, which is public and set in 
stone?

--
Davide
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

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

[lldb-dev] [Bug 23588] lldb command line tool won't run on OSX 10.9.5 without DYLD_FRAMEWORK_PATH set to directory containing LLDB.framework

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #2 from Jonas Devlieghere  ---
I cannot reproduce this.

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

Re: [lldb-dev] Cannot use system debugserver for testing

[Gábor Márton via lldb-dev]

This might not be related to the debugserver, I just realized that I get
"error: process exited with status -1 (Error 1)"
even with the simplest main.c.
This may be some kind of security issue on mac OS...
Though I've checked and I have SIP disabled and I have executed "sudo
/usr/sbin/DevToolsSecurity --enable".

On Fri, Jul 19, 2019 at 4:46 PM Gábor Márton  wrote:

> Hi Stefan,
>
> Since the commit
> "[CMake] Always build debugserver on Darwin and allow tests to use the
> system's one"
> I cannot use the system debugserver for testing.
> I receive the following error message from lldb when I execute "ninja
> check-lldb":
> ```
> runCmd: run
> runCmd failed!
> error: process exited with status -1 (Error 1)
> ```
>
> I do set up "-DLLDB_USE_SYSTEM_DEBUGSERVER=ON" with cmake so I see
> ```
> -- LLDB tests use out-of-tree debugserver:
> /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Resources/debugserver
> ```
>
> Also, I have inspected the following test output
> ```
> Command invoked: /usr/bin/python
> /Users/egbomrt/llvm2/git/llvm/tools/lldb/test/dotest.py -q --arch=x86_64 -s
> /Users/egbomrt/llvm2/build/release_assert/lldb-test-traces --build-dir
> /Users/egbomrt/llvm2/build/release_assert/lldb-test-build.noindex -S nm -u
> CXXFLAGS -u CFLAGS --executable
> /Users/egbomrt/llvm2/build/release_assert/./bin/lldb --dsymutil
> /Users/egbomrt/llvm2/build/release_assert/./bin/dsymutil --filecheck
> /Users/egbomrt/llvm2/build/release_assert/./bin/FileCheck -C
> /Users/egbomrt/llvm2/build/release_assert/bin/clang --codesign-identity -
> --out-of-tree-debugserver --arch x86_64 -t --env TERM=vt100 -p
> TestCModules.py --results-port 49931 -S nm --inferior -p TestCModules.py
> /Users/egbomrt/llvm2/git/llvm/tools/lldb/packages/Python/lldbsuite/test/lang/c/modules
> --event-add-entries worker_index=0:int
>   1 out of 736 test suites processed - TestCModules.py
> ```
> so it seems like the argument for --out-of-tree-debugserver is missing...
>
> Could you please advise?
>
> Thank you,
> Gabor
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] Cannot use system debugserver for testing

[Gábor Márton via lldb-dev]

Actually, it is embarrassing (perhaps for macOS and not for me) that after
a reboot the problem is gone.
Perhaps after "sudo /usr/sbin/DevToolsSecurity --enable" a reboot is
required, but could not find anything official about that.

On Fri, Jul 19, 2019 at 7:20 PM Gábor Márton  wrote:

> This might not be related to the debugserver, I just realized that I get
> "error: process exited with status -1 (Error 1)"
> even with the simplest main.c.
> This may be some kind of security issue on mac OS...
> Though I've checked and I have SIP disabled and I have executed "sudo
> /usr/sbin/DevToolsSecurity --enable".
>
> On Fri, Jul 19, 2019 at 4:46 PM Gábor Márton 
> wrote:
>
>> Hi Stefan,
>>
>> Since the commit
>> "[CMake] Always build debugserver on Darwin and allow tests to use the
>> system's one"
>> I cannot use the system debugserver for testing.
>> I receive the following error message from lldb when I execute "ninja
>> check-lldb":
>> ```
>> runCmd: run
>> runCmd failed!
>> error: process exited with status -1 (Error 1)
>> ```
>>
>> I do set up "-DLLDB_USE_SYSTEM_DEBUGSERVER=ON" with cmake so I see
>> ```
>> -- LLDB tests use out-of-tree debugserver:
>> /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Resources/debugserver
>> ```
>>
>> Also, I have inspected the following test output
>> ```
>> Command invoked: /usr/bin/python
>> /Users/egbomrt/llvm2/git/llvm/tools/lldb/test/dotest.py -q --arch=x86_64 -s
>> /Users/egbomrt/llvm2/build/release_assert/lldb-test-traces --build-dir
>> /Users/egbomrt/llvm2/build/release_assert/lldb-test-build.noindex -S nm -u
>> CXXFLAGS -u CFLAGS --executable
>> /Users/egbomrt/llvm2/build/release_assert/./bin/lldb --dsymutil
>> /Users/egbomrt/llvm2/build/release_assert/./bin/dsymutil --filecheck
>> /Users/egbomrt/llvm2/build/release_assert/./bin/FileCheck -C
>> /Users/egbomrt/llvm2/build/release_assert/bin/clang --codesign-identity -
>> --out-of-tree-debugserver --arch x86_64 -t --env TERM=vt100 -p
>> TestCModules.py --results-port 49931 -S nm --inferior -p TestCModules.py
>> /Users/egbomrt/llvm2/git/llvm/tools/lldb/packages/Python/lldbsuite/test/lang/c/modules
>> --event-add-entries worker_index=0:int
>>   1 out of 736 test suites processed - TestCModules.py
>> ```
>> so it seems like the argument for --out-of-tree-debugserver is missing...
>>
>> Could you please advise?
>>
>> Thank you,
>> Gabor
>>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [RFC] Removing lldb-mi

[Raphael “Teemperor” Isemann via lldb-dev]

The expected way as of now is to compile lldb-mi against an installed lldb 
(either a compiled version or whatever your OS/package manager provides). The 
CMake file will automatically find LLDB and build against it. See the travis CI 
script[1] in the repo on how that looks in practice.

The problem with the tests is that:

1. They (randomly) fail, which is why we already disabled most (all?) of them 
even before we removed lldb-mi. That’s mostly because of lldb-mi bugs and the 
way the tests were implemented from what I understand.
2. They depend on the LLDB python testing logic which isn’t as trivial to port 
over to the standalone lldb-mi repo. And the testing logic also not distributed 
with LLDB.

So after some discussion we decided that we don’t port the tests over as it’s 
just not worth it. The ideal outcome would be that someone writes a new set of 
tests that are is stable than the ones we had.

- Raphael

[1] https://github.com/lldb-tools/lldb-mi/blob/master/ci/travis.sh


> On Jul 19, 2019, at 6:34 PM, Ted Woodward  wrote:
> 
> As of yesterday, lldb-mi has been removed from lldb and moved to 
> https://github.com/lldb-tools/lldb-mi  
> .
>  
> Some questions:
> Is the expected way to build lldb-mi to drop the lldb-tools/lldb-mi repo into 
> /tools/lldb-mi?
> The lldb-mi tests weren’t moved into the new repo on github. Do we plan on 
> moving them?
> If we don’t move them, do we just rely on the lldb-mi executable not existing 
> to keep from trying to run them?
> If we do move them, how do we run them?
>  
> Ted
>  
> From: lldb-dev  On Behalf Of Jonas 
> Devlieghere via lldb-dev
> Sent: Friday, July 5, 2019 11:44 AM
> To: Raphael “Teemperor” Isemann 
> Cc: LLDB 
> Subject: [EXT] Re: [lldb-dev] [RFC] Removing lldb-mi
>  
> Thank you for doing this, Raphael. I believe this shows that it's possible to 
> keep lldb-mi alive, without today's maintenance burden on the LLDB community, 
> a solution that seems to appease everyones concerns in this thread. I hope 
> this sparks interest for somebody to step up as a maintainer. 
>  
> I went ahead and created a diff to add the proposed deprecations to the LLVM 
> release notes: https://reviews.llvm.org/D64254 
>  
> I'll put up another diff to remove the code, which we can land once LLVM 9 
> has branched. 
>  
> Thank you,
> Jonas
>  
> On Thu, Jul 4, 2019 at 12:24 PM Raphael “Teemperor” Isemann via lldb-dev 
> mailto:lldb-dev@lists.llvm.org>> wrote:
> I just went forward with this and made a quick test repo with an out-of-tree 
> lldb-mi that compiles against the system 
> LLDB:https://github.com/Teemperor/lldb-mi 
>  This seems to work fine with the 
> exception of the python tests which require LLDB’s python code for testing 
> which isn’t installed alongside LLDB. I guess we will have to see if we copy 
> the related test code there or we just rewrite the test suite (which is 
> anyway broken). On the upside, we can now just use Travis for CI as we don’t 
> have to compile LLVM/Clang/LLDB, so that’s nice.
>  
> I’m in favor of deprecating lldb-mi with 9.0.0 and then we can give 
> downstream time until 10.0.0 (or X.0.0 :) ) to package out-of-tree lldb-mi 
> for users. Given how simple lldb-mi is, this seems like a reasonable 
> timeframe.
>  
> - Raphael
>  
>  
> On Jul 4, 2019, at 9:51 AM, Davide Italiano via lldb-dev 
> mailto:lldb-dev@lists.llvm.org>> wrote:
>  
>  
>  
> On Thu, Jul 4, 2019 at 12:58 AM Zdenek Prikryl via lldb-dev 
> mailto:lldb-dev@lists.llvm.org>> wrote:
> We're using it with Eclipse and Eclipse based product, so I'd like to keep as 
> well! :-)...
> 
> Zdenek
> 
>  
> I do understand that there's desire from people to keep this around (from an 
> user perspective), but I guess this fundamentally misses Jonas' original mail 
> point.
> lldb-mi has been unmaintained for a long time (at least the past two years 
> from what I can tell), and we tried to use it in emacs without success.
> It has never been a priority for many of the parties putting effort in lldb 
> and I'm under the impression the situation won't change in the foreseeable 
> future.
> Unless somebody steps up as maintainer I don't think there's a lot of future 
> for the tool. 
> Maybe a good compromise would be that of having lldb-mi living in a separate 
> repo somewhere on GitHub, as it only uses the SBAPI, which is public and set 
> in stone?
>  
> --
> Davide
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org 
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev 
> 
>  
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org 
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev 
> 

Re: [lldb-dev] Cannot use system debugserver for testing

[Jonas Devlieghere via lldb-dev]

I this was because of a change in llvm which broke codesigning of
debugserver: https://reviews.llvm.org/D64965

On Fri, Jul 19, 2019 at 10:36 AM Gábor Márton via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> Actually, it is embarrassing (perhaps for macOS and not for me) that after
> a reboot the problem is gone.
> Perhaps after "sudo /usr/sbin/DevToolsSecurity --enable" a reboot is
> required, but could not find anything official about that.
>
> On Fri, Jul 19, 2019 at 7:20 PM Gábor Márton 
> wrote:
>
>> This might not be related to the debugserver, I just realized that I get
>> "error: process exited with status -1 (Error 1)"
>> even with the simplest main.c.
>> This may be some kind of security issue on mac OS...
>> Though I've checked and I have SIP disabled and I have executed "sudo
>> /usr/sbin/DevToolsSecurity --enable".
>>
>> On Fri, Jul 19, 2019 at 4:46 PM Gábor Márton 
>> wrote:
>>
>>> Hi Stefan,
>>>
>>> Since the commit
>>> "[CMake] Always build debugserver on Darwin and allow tests to use the
>>> system's one"
>>> I cannot use the system debugserver for testing.
>>> I receive the following error message from lldb when I execute "ninja
>>> check-lldb":
>>> ```
>>> runCmd: run
>>> runCmd failed!
>>> error: process exited with status -1 (Error 1)
>>> ```
>>>
>>> I do set up "-DLLDB_USE_SYSTEM_DEBUGSERVER=ON" with cmake so I see
>>> ```
>>> -- LLDB tests use out-of-tree debugserver:
>>> /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Resources/debugserver
>>> ```
>>>
>>> Also, I have inspected the following test output
>>> ```
>>> Command invoked: /usr/bin/python
>>> /Users/egbomrt/llvm2/git/llvm/tools/lldb/test/dotest.py -q --arch=x86_64 -s
>>> /Users/egbomrt/llvm2/build/release_assert/lldb-test-traces --build-dir
>>> /Users/egbomrt/llvm2/build/release_assert/lldb-test-build.noindex -S nm -u
>>> CXXFLAGS -u CFLAGS --executable
>>> /Users/egbomrt/llvm2/build/release_assert/./bin/lldb --dsymutil
>>> /Users/egbomrt/llvm2/build/release_assert/./bin/dsymutil --filecheck
>>> /Users/egbomrt/llvm2/build/release_assert/./bin/FileCheck -C
>>> /Users/egbomrt/llvm2/build/release_assert/bin/clang --codesign-identity -
>>> --out-of-tree-debugserver --arch x86_64 -t --env TERM=vt100 -p
>>> TestCModules.py --results-port 49931 -S nm --inferior -p TestCModules.py
>>> /Users/egbomrt/llvm2/git/llvm/tools/lldb/packages/Python/lldbsuite/test/lang/c/modules
>>> --event-add-entries worker_index=0:int
>>>   1 out of 736 test suites processed - TestCModules.py
>>> ```
>>> so it seems like the argument for --out-of-tree-debugserver is missing...
>>>
>>> Could you please advise?
>>>
>>> Thank you,
>>> Gabor
>>>
>> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 32053] lldb-mi outputs extra =thread-group-exited after -gdb-exit

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 38880] lldb-mi -exec-jump not implemented

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #17 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28253] lldb-mi Regression with LLDB_DISABLE_PYTHON=1

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #6 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 31485] LLDB-MI: data-disassemble command doesn't follow target.x86-disassemble-flavor setting

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com
 Resolution|--- |MOVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 36156] lldb-mi does not report watchpoint stops

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com
 Resolution|--- |MOVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28858] LLDB-MI: no notification about process stopped if attaching to a process

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 30423] [lldb-mi] -var-assign doesn't evaluate the expression to assign

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28718] LLDB-MI: disassembly-flavor not supported by gdb-set and gdb-show

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #2 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28860] LLDB-MI: no breakpoint-modified notification when a breakpoint is hit

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28859] LLDB-MI: data-disassemble command doesn't accept "$pc" as start and end address parameter

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28698] [lldb-mi] -break-insert with -f (pending flag) requires additional parameter

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #2 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28857] LLDB-MI: break-enable doesn't enable specified breakpoints

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28703] LLDB-MI: break-insert command flag -d (disabled) has no effect when combined with -f (pending)

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28702] LLDB-MI: pending break point set with command break-insert -f doesn't get resolved

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |MOVED
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #2 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 25000] lldb-mi does not receive broadcasted notification from Core/Process about process stopped if StopAtEntry was requested ("process launch -s" OR "-exec-run --start")

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 28621] 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://bugs.llvm.org/show_bug.cgi?id=28621

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 20685] vim-lldb fails on MacOS X Mavericks

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Jonas Devlieghere  ---
I don't think there's anything for us to be done here.

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

[lldb-dev] [Bug 21736] memory read assertion failure with -f a -s 32

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
Process 58989 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #0: 0x00010f9f a.out`main at main.cpp:9:12
   6  void f(S2 &M1);
   7};
   8
-> 9struct S2 { int x; };
   10
   11   }
   12
(lldb) memory read -f a -s 32 `$rbp` `$rbp + 0x30`
0x7ffeefbff620: error: unsupported byte size (32) for char format
(lldb) memory read -f a -s 64 `$rbp` `$rbp + 0x30`

(lldb)

This now prints nothing, but it doesn't trigger the assertion.

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

[lldb-dev] [Bug 23506] Segmentation fault from "frame variable" command

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
Insufficient information.

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

[lldb-dev] [Bug 24198] template enum parameter incorrectly mangled during expression evaluation

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
Process 70212 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #0: 0x00010fad a.out`main at main.cpp:19:5
   16   {
   17   TCTest ToTest;
   18   &TCTest::ms_Value;
-> 19   return 0;
   20   }
(lldb) expr ToTest.ms_Value
(ETest) $0 = ETest_1

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

[lldb-dev] [Bug 28016] Assertion failed: (false && "Unhandled quote character")

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
This behaves correctly for me with ToT.

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

[lldb-dev] [Bug 28953] Xcode build: be explicit about which clang and LLVM .a files get linked into LLDB

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
This was landed in r278527.

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

[lldb-dev] [Bug 21390] crashlog.py does not use alternate source paths

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #2 from Jonas Devlieghere  ---


*** This bug has been marked as a duplicate of bug 21391 ***

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

[lldb-dev] [Bug 19974] C: lldb cant find file:line in "included" code (set breakpoint / source list)

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com
 Resolution|--- |WORKSFORME

--- Comment #3 from Jonas Devlieghere  ---
(lldb) target create "./x"
Current executable set to './x' (x86_64).
(lldb) b x1.c:3
Breakpoint 1: where = x`x1 + 8 at x1.c:3:3, address = 0x00010f58
(lldb) b x.c:6
Breakpoint 2: where = x`main + 39 at x.c:6:3, address = 0x00010f27
(lldb) source list -f x.c -l 3
   3int main(int argc, char **argv)
   4{
   5  printf("main starts\n");
   6  x1();
   7  printf("main exiting\n");
   8  return 0;
   9}
   10   #include "x1.c"
(lldb) source list -f x1.c -l 1
error: Could not find source file "x1.c".
(lldb) breakpoint set -name x1
Breakpoint 3: where = x`x1 + 8 at x1.c:3:3, address = 0x00010f58

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

[lldb-dev] [Bug 27861] TestObjCMethods2.py - test_NSString_expr_commands_gmodules() fails

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #1 from Jonas Devlieghere  ---
Fixed by r270848

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

Re: [lldb-dev] Cannot use system debugserver for testing

[Stefan Gränitz via lldb-dev]

Hi Gábor, I am sorry this caused an issue for you. Good that apparently
it's resolved now.

Did you reconfigure an existing build-tree? Your observations would make
sense in this context, because the change affects CMake cached
variables. This is unfortunate, but can not always be avoided. If this
happens again (or to anyone else), a clean build seems to be a good
first step.

Best,
Stefan

On 19/07/2019 19:36, Gábor Márton wrote:

> Actually, it is embarrassing (perhaps for macOS and not for me) that
> after a reboot the problem is gone.
> Perhaps after "sudo /usr/sbin/DevToolsSecurity --enable" a reboot is
> required, but could not find anything official about that.
>
> On Fri, Jul 19, 2019 at 7:20 PM Gábor Márton  > wrote:
>
> This might not be related to the debugserver, I just realized that
> I get 
> "error: process exited with status -1 (Error 1)"
> even with the simplest main.c.
> This may be some kind of security issue on mac OS...
> Though I've checked and I have SIP disabled and I have executed
> "sudo /usr/sbin/DevToolsSecurity --enable".
>
> On Fri, Jul 19, 2019 at 4:46 PM Gábor Márton
> mailto:martongab...@gmail.com>> wrote:
>
> Hi Stefan,
>
> Since the commit
> "[CMake] Always build debugserver on Darwin and allow tests to
> use the system's one"
> I cannot use the system debugserver for testing.
> I receive the following error message from lldb when I execute
> "ninja check-lldb":
> ```
> runCmd: run
> runCmd failed!
> error: process exited with status -1 (Error 1)
> ```
>
> I do set up "-DLLDB_USE_SYSTEM_DEBUGSERVER=ON" with cmake so I see
> ```
> -- LLDB tests use out-of-tree debugserver:
> 
> /Library/Developer/CommandLineTools/Library/PrivateFrameworks/LLDB.framework/Resources/debugserver
> ```
>
> Also, I have inspected the following test output
> ```
> Command invoked: /usr/bin/python
> /Users/egbomrt/llvm2/git/llvm/tools/lldb/test/dotest.py -q
> --arch=x86_64 -s
> /Users/egbomrt/llvm2/build/release_assert/lldb-test-traces
> --build-dir
> /Users/egbomrt/llvm2/build/release_assert/lldb-test-build.noindex
> -S nm -u CXXFLAGS -u CFLAGS --executable
> /Users/egbomrt/llvm2/build/release_assert/./bin/lldb
> --dsymutil
> /Users/egbomrt/llvm2/build/release_assert/./bin/dsymutil
> --filecheck
> /Users/egbomrt/llvm2/build/release_assert/./bin/FileCheck -C
> /Users/egbomrt/llvm2/build/release_assert/bin/clang
> --codesign-identity - --out-of-tree-debugserver --arch x86_64
> -t --env TERM=vt100 -p TestCModules.py --results-port 49931 -S
> nm --inferior -p TestCModules.py
> 
> /Users/egbomrt/llvm2/git/llvm/tools/lldb/packages/Python/lldbsuite/test/lang/c/modules
> --event-add-entries worker_index=0:int
>   1 out of 736 test suites processed - TestCModules.py
> ```
> so it seems like the argument for --out-of-tree-debugserver is
> missing...
>
> Could you please advise?
>
> Thank you,
> Gabor
>
-- 
https://flowcrypt.com/pub/stefan.graen...@gmail.com

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

[lldb-dev] [Bug 37054] MI '-info sharedlibrary' command crash

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Resolution|--- |MOVED
 Status|NEW |RESOLVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 25446] lldb Python extension module is linked to libpython

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Resolution|--- |WONTFIX
 Status|NEW |RESOLVED

--- Comment #4 from Jonas Devlieghere  ---
This issue was closed downstream.

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

[lldb-dev] [Bug 25049] Bootstrapping LLDB fails on recent OSX due to c++11-narrowing

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED

--- Comment #4 from Jonas Devlieghere  ---
This doesn't seem relevant anymore, at least I cannot reproduce this.

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

[lldb-dev] [Bug 23978] "-data-disassemble -s start -e end" MI command disassembles (end-start) *instructions*

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 23248] "stopped" notification for the exec-finish GDB/MI command gives the wrong reason

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 CC||jdevliegh...@apple.com
 Status|CONFIRMED   |RESOLVED
 Resolution|--- |MOVED

--- Comment #2 from Jonas Devlieghere  ---
lldb-mi is no longer part of the lldb repository.

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

[lldb-dev] [Bug 22784] pexpect tests failing on FreeBSD buildbot

[via lldb-dev]

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

Jonas Devlieghere  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|NEW |RESOLVED
 CC||jdevliegh...@apple.com

--- Comment #2 from Jonas Devlieghere  ---


*** This bug has been marked as a duplicate of bug 25172 ***

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

Re: [lldb-dev] "error: summary string parsing error" on Fedora 30

[Greg Clayton via lldb-dev]

Sounds like the compiler omitted the type info for std::string. Try "-glldb" in 
your compiler flags. This tunes debug info for LLDB. A lot of compilers will 
try to omit types from debug info if the type doesn't originate in the current 
executable. std::string would be one of those classes. If that flag doesn't 
work, then you might try -fno-limit-debug-info.

Let me know if that helps!

> On Jul 18, 2019, at 5:45 PM, Bob Eastbrook  wrote:
> 
> Thanks for the info.  "frame var --raw msg" is empty on my Fedora 30
> system, but populated correctly on Ubuntu 19.04.  E.g., on Fedora 30:
> 
> (lldb) frame var --raw msg
> (std::string) msg = {}
> 
> I compiled with "clang++ -g main.cpp".  Nothing fancy.  Installed
> Clang with "dnf install clang".  Again, nothing fancy.
> 
> I'm a LLVM newb.  Can you point me in the right direction?
> 
> 
> 
> 
> On Fri, Jul 12, 2019 at 1:56 PM Greg Clayton  wrote:
>> 
>> We have a summary provider for std::string that is built into LLDB that must 
>> not be working with the C++ runtime you are using. The current summary 
>> string that is used is in 
>> source/Plugins/Language/CPlusPlus/CPlusPlusLanguage.cpp in 
>> LoadLibStdcppFormatters:
>> 
>>  lldb::TypeSummaryImplSP std_string_summary_sp(
>>  new StringSummaryFormat(stl_summary_flags, "${var._M_dataplus._M_p}"));
>> 
>> So do a "frame var --raw msg" and see what the members of your std::string 
>> look like. I am guessing you won't see "_M_dataplus" or "_M_p" in there. The 
>> "${var" means your std::string variable, and we are trying to access 
>> "msg._M_dataplus._M_p" to see what the string looks like.
>> 
>> 
>> On Jun 24, 2019, at 10:26 PM, Bob Eastbrook via lldb-dev 
>>  wrote:
>> 
>> With Clang 8.0.0 and libstd++ 9.1.1 on Fedora 30 x86_64, I get this
>> error from LLDB when trying to see the value of a string:
>> 
>> "error: summary string parsing error"
>> 
>> The code is simply:
>> 
>> std::string msg{"foo bar baz"};
>> 
>> With libcxx 8.0.0, instead of the above error, I simply see "??" when
>> inspecting the msg variable.
>> 
>> All of the above works fine for me in Ubuntu 19.04. I only have the
>> problem with Fedora 30.  Tried in both CLion and VS Code.
>> 
>> How should I troubleshoot this?  Could I be missing a package?
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>> 
>> 

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

[lldb-dev] 8.0.1-final has been tagged

[Tom Stellard via lldb-dev]

Hi,

The 8.0.1 final release has been tagged.  Testers please upload the final
binaries.

-Tom
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev