David Greene via llvm-dev writes:
> Now that I think about it, what you really want is something that runs
> migrate-downstream-fork.py on the commits in llvm and something that
> runs zip-downstream-fork.py on commits in other projects, but they have
> to ruin simultaneously to keep the commits
https://bugs.llvm.org/show_bug.cgi?id=38373
Stella Stamenova changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.llvm.org/show_bug.cgi?id=21550
Stella Stamenova changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
Hi lldb-dev,
Could someone explain me why do we use python (OperatingSystemPython) to
describe OS objects like threads? What are the advantages of such an
approach in comparison to C++ used in Platform plugin for example? IMO, the
OperatingSystem plugin could be more like the Platform one, it coul
You would use an operating system plugin in cases where the underlying process
interface doesn't tell the complete story for the OS threads. For instance, a
lot of kernel and bare board OS'es have a gdb-remote stub that just describes
the state of the threads currently running on the cores of t
Hi,
I've tagged the 7.0.1 final release. Testers may begin uploading binaries.
-Tom
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=24600
Stella Stamenova changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
