Thank you Jim and Greg, for your help. I will be careful with threads and I
will also switch to using launch info.
Kind regards
Jayvee
Am Do., 18. Juli 2019 um 19:19 Uhr schrieb Jim Ingham :
> The main problem with trying to run a debug session multithreaded is
> coordinating execution control.
https://bugs.llvm.org/show_bug.cgi?id=19316
Jonas Devlieghere changed:
What|Removed |Added
CC||jdevliegh...@apple.com
Status|N
https://bugs.llvm.org/show_bug.cgi?id=20266
Jonas Devlieghere changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugs.llvm.org/show_bug.cgi?id=20264
Jonas Devlieghere changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugs.llvm.org/show_bug.cgi?id=20260
Jonas Devlieghere changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://bugs.llvm.org/show_bug.cgi?id=17722
Jonas Devlieghere changed:
What|Removed |Added
Resolution|--- |WORKSFORME
CC|
https://bugs.llvm.org/show_bug.cgi?id=17502
Jonas Devlieghere changed:
What|Removed |Added
Resolution|--- |WONTFIX
CC|
https://bugs.llvm.org/show_bug.cgi?id=15879
Jonas Devlieghere changed:
What|Removed |Added
CC||jdevliegh...@apple.com
Status|N
https://bugs.llvm.org/show_bug.cgi?id=15401
Jonas Devlieghere changed:
What|Removed |Added
Resolution|--- |WORKSFORME
CC|
https://bugs.llvm.org/show_bug.cgi?id=13908
Jonas Devlieghere changed:
What|Removed |Added
CC||jdevliegh...@apple.com
Resolution|-
https://bugs.llvm.org/show_bug.cgi?id=13568
Jonas Devlieghere changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
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, no
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 qu
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,
The main problem with trying to run a debug session multithreaded is
coordinating execution control. Thread A gets a variable list and iterates
over it to get child values. Thread B issues a "step" command. The API's
thread A calls will either fail (because the target is running) or maybe fet
> On Jul 18, 2019, at 4:00 AM, Jayvee Neumann wrote:
>
> Thank you for your help.
>
> What is the reason for using SBLaunchInfo over calling tgt.Launch with the
> launch configuration as a set of parameters?
The code is much clearer on what arguments mean what. In your current launch
call,
Hello everyone,
The release branch for LLVM 9 and its sub-projects was just created
from trunk at r366426, and the trunk version was subsequently bumped
to 10.0.0.
Release blockers are tracked by https://llvm.org/PR42474 Please mark
any bugs, old or new, that need to be fixed before the release a
Thank you for your help.
What is the reason for using SBLaunchInfo over calling tgt.Launch with the
launch configuration as a set of parameters? Furthermore I do not see a way
to set stdout, stdin, and stderr for the launched process by using
SBLaunchInfo.
I have a question regarding the event lo
18 matches
Mail list logo
