Page MenuHomePhabricator

mgorny (Michał Górny)
User

Projects

User does not belong to any projects.

User Details

User Since
Aug 15 2016, 6:00 AM (161 w, 6 d)

Recent Activity

Today

mgorny added a comment to D67583: Fix swig python package path.

This will work for the python-in-lldb case. However, the idea is lldb can also be used as python package, from any python application (by just typing import lldb). For that to work, we need to install lldb python stuff to a location that will be searched for by python in its default configuration.

Mon, Sep 23, 1:05 AM · Restricted Project, Restricted Project

Yesterday

mgorny requested changes to D67866: [lldb] Unify python site-packages path.

I do not believe this to be the right approach. Unconditionally installing Python modules to the wrong directory is a bug, not a feature. It should be fixed (as I proposed in D67890), not made more prominent by making everything hinge on it.

Sun, Sep 22, 11:03 PM · Restricted Project
mgorny committed rG96f35266a5d6: [clang] [Basic] Enable __has_feature(leak_sanitizer) (authored by mgorny).
[clang] [Basic] Enable __has_feature(leak_sanitizer)
Sun, Sep 22, 1:55 PM
mgorny committed rL372527: [clang] [Basic] Enable __has_feature(leak_sanitizer).
[clang] [Basic] Enable __has_feature(leak_sanitizer)
Sun, Sep 22, 1:53 PM
mgorny closed D67719: [clang] [Basic] Enable __has_feature(leak_sanitizer).
Sun, Sep 22, 1:53 PM · Restricted Project
mgorny created D67890: [lldb] [cmake] Fix installing Python modules on systems using /usr/lib.
Sun, Sep 22, 8:37 AM

Sat, Sep 21

mgorny added a comment to D66176: Fix Driver/modules.cpp test to work when build directory name contains '.s'.

Ping. This is a really silly issue, and one that could be fixed trivially, so it'd be really nice to actually fix it.

Sat, Sep 21, 2:00 AM · Restricted Project

Fri, Sep 20

mgorny updated the diff for D67719: [clang] [Basic] Enable __has_feature(leak_sanitizer).

Test added. Thanks for the suggestion!

Fri, Sep 20, 11:22 PM · Restricted Project
mgorny added a comment to D64647: <WIP> [lldb] [Process/NetBSD] Multithread support.

Nevermind that long report, it actually turned out to be a bug in NetBSD kernel that resulted in the thread not being resumed.

Fri, Sep 20, 11:17 PM · Restricted Project

Thu, Sep 19

mgorny added a comment to D64647: <WIP> [lldb] [Process/NetBSD] Multithread support.

So I've made some progress on this. However, I'm stuck and I'd use some help going forward.

Thu, Sep 19, 8:36 AM · Restricted Project
mgorny updated the diff for D64647: <WIP> [lldb] [Process/NetBSD] Multithread support.
Thu, Sep 19, 8:18 AM · Restricted Project
mgorny abandoned D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP].

The problem is to complex too be implemented in smaller blocks. I'm going to close this in favor of a single unified patch in D64647.

Thu, Sep 19, 8:17 AM

Wed, Sep 18

mgorny committed rGc36b0bf31067: [lldb] [Process/gdb-remote] Correct more missing LLDB_INVALID_SIGNAL_NUMBER (authored by mgorny).
[lldb] [Process/gdb-remote] Correct more missing LLDB_INVALID_SIGNAL_NUMBER
Wed, Sep 18, 10:55 PM
mgorny committed rL372300: [lldb] [Process/gdb-remote] Correct more missing LLDB_INVALID_SIGNAL_NUMBER.
[lldb] [Process/gdb-remote] Correct more missing LLDB_INVALID_SIGNAL_NUMBER
Wed, Sep 18, 10:54 PM
mgorny closed D67727: [lldb] [Process/gdb-remote] Correct more missing LLDB_INVALID_SIGNAL_NUMBER.
Wed, Sep 18, 10:54 PM · Restricted Project
mgorny created D67727: [lldb] [Process/gdb-remote] Correct more missing LLDB_INVALID_SIGNAL_NUMBER.
Wed, Sep 18, 12:17 PM · Restricted Project
mgorny created D67719: [clang] [Basic] Enable __has_feature(leak_sanitizer).
Wed, Sep 18, 9:53 AM · Restricted Project

Tue, Sep 17

mgorny committed rGe4d25e9e1627: [lldb] [Process/gdb-remote] Fix defaulting signal to invalid in action list (authored by mgorny).
[lldb] [Process/gdb-remote] Fix defaulting signal to invalid in action list
Tue, Sep 17, 2:33 AM
mgorny committed rL372090: [lldb] [Process/gdb-remote] Fix defaulting signal to invalid in action list.
[lldb] [Process/gdb-remote] Fix defaulting signal to invalid in action list
Tue, Sep 17, 2:29 AM
mgorny closed D67625: [lldb] [Process/gdb-remote] Fix defaulting signal to invalid in action list.
Tue, Sep 17, 2:29 AM · Restricted Project

Mon, Sep 16

mgorny created D67625: [lldb] [Process/gdb-remote] Fix defaulting signal to invalid in action list.
Mon, Sep 16, 8:41 AM · Restricted Project

Sat, Sep 14

mgorny added a comment to D67585: [clang] [cmake] Make building dylib optional.

But in that case, we should aim for consistency, i.e. remove the matching option from LLVM.

Sat, Sep 14, 11:46 AM
mgorny added a comment to D67585: [clang] [cmake] Make building dylib optional.

Sure but I want to build-test practically everything else. I wouldn't mind if this didn't basically kill my test system by resource exhaustion

You can use the ‘LLVM_DISTRIBUTION_COMPONENTS’ option to create a build test target that includes the things you care to test.

Sat, Sep 14, 9:33 AM
mgorny added a comment to D67585: [clang] [cmake] Make building dylib optional.

Also note that I'm leaving it enabled by default, so only people explicitly opting out would not be testing it.

Sat, Sep 14, 9:16 AM
mgorny added a comment to D67585: [clang] [cmake] Make building dylib optional.

Sure but I want to build-test practically everything else. I wouldn't mind if this didn't basically kill my test system by resource exhaustion.

Sat, Sep 14, 9:15 AM
mgorny created D67585: [clang] [cmake] Make building dylib optional.
Sat, Sep 14, 3:41 AM

Thu, Sep 12

mgorny committed rGbfb5b0cb86cf: [clang] [unittest] Import LLVMTestingSupport if necessary (authored by mgorny).
[clang] [unittest] Import LLVMTestingSupport if necessary
Thu, Sep 12, 6:06 AM
mgorny committed rL371733: [clang] [unittest] Import LLVMTestingSupport if necessary.
[clang] [unittest] Import LLVMTestingSupport if necessary
Thu, Sep 12, 6:06 AM
mgorny closed D67452: [clang] [unittest] Import LLVMTestingSupport if necessary.
Thu, Sep 12, 6:05 AM · Restricted Project
mgorny added a comment to D67452: [clang] [unittest] Import LLVMTestingSupport if necessary.

Thanks. Could you also ack the backport in https://bugs.llvm.org/show_bug.cgi?id=43281?

Thu, Sep 12, 6:05 AM · Restricted Project

Wed, Sep 11

mgorny created D67452: [clang] [unittest] Import LLVMTestingSupport if necessary.
Wed, Sep 11, 9:51 AM · Restricted Project

Mon, Sep 9

mgorny added a comment to D66390: [PATCH] [llvm] [Support] Update license on ConvertUTF.* per upstream license change.

Reping.

Mon, Sep 9, 10:51 PM · Restricted Project

Thu, Sep 5

mgorny added a comment to D63672: Added Delta IR Reduction Tool.

Ok, I have an idea of using --test-arg but it would require the args to be passed before the filename. I'll post a patch.

Actually, I won't because I'm hitting some memory corruption in TestArgs and I don't really have time or motivation to fight it. Please fix your code.

Could you be more specific? I've tried running both tests under valgrind and haven't encountered any reported errors there.

Thu, Sep 5, 10:38 PM · Restricted Project

Wed, Sep 4

mgorny added a comment to D62868: [libc++] Always build with -fvisibility=hidden.

Thanks. It seems to fix the test I used to bisect this. It will take some time before buildbot confirms this but I'm going to presume it's good now. If it fails more, I'll ping you.

Wed, Sep 4, 10:07 AM · Restricted Project, Restricted Project
mgorny added a comment to D63672: Added Delta IR Reduction Tool.

Ok, I have an idea of using --test-arg but it would require the args to be passed before the filename. I'll post a patch.

Wed, Sep 4, 4:28 AM · Restricted Project
mgorny added a comment to D63672: Added Delta IR Reduction Tool.

Ok, I have an idea of using --test-arg but it would require the args to be passed before the filename. I'll post a patch.

Wed, Sep 4, 4:11 AM · Restricted Project

Tue, Sep 3

mgorny committed rG37f91c32186a: [lldb] [test] Mark 'reenabled' tests XFAIL on NetBSD (authored by mgorny).
[lldb] [test] Mark 'reenabled' tests XFAIL on NetBSD
Tue, Sep 3, 11:40 PM
mgorny committed rL370842: [lldb] [test] Mark 'reenabled' tests XFAIL on NetBSD.
[lldb] [test] Mark 'reenabled' tests XFAIL on NetBSD
Tue, Sep 3, 11:40 PM
mgorny added a comment to D63672: Added Delta IR Reduction Tool.

This broke NetBSD buildbots:
http://lab.llvm.org:8011/builders/netbsd-amd64/builds/22010/steps/run%20unit%20tests/logs/FAIL%3A%20LLVM%3A%3Aremove-funcs.ll
http://lab.llvm.org:8011/builders/netbsd-amd64/builds/22010/steps/run%20unit%20tests/logs/FAIL%3A%20LLVM%3A%3Aremove-global-vars.ll

Tue, Sep 3, 11:31 PM · Restricted Project
mgorny committed rG3461e3ea8eb7: [lldb] [test] Un-mark two commands/register tests XFAIL (authored by mgorny).
[lldb] [test] Un-mark two commands/register tests XFAIL
Tue, Sep 3, 11:15 PM
mgorny committed rL370840: [lldb] [test] Un-mark two commands/register tests XFAIL.
[lldb] [test] Un-mark two commands/register tests XFAIL
Tue, Sep 3, 11:08 PM
mgorny added a comment to D62868: [libc++] Always build with -fvisibility=hidden.

Quick update for watchers:

The bug mentioned by Peter has been fixed now, but I'm looking into other link errors when using GCC (because there's more).

Tue, Sep 3, 10:22 PM · Restricted Project, Restricted Project
mgorny committed rG3276fffc1700: [lldb] Replace std::call_once() with llvm::call_once() (authored by mgorny).
[lldb] Replace std::call_once() with llvm::call_once()
Tue, Sep 3, 6:01 AM
mgorny committed rL370748: [lldb] Replace std::call_once() with llvm::call_once().
[lldb] Replace std::call_once() with llvm::call_once()
Tue, Sep 3, 5:33 AM

Mon, Sep 2

mgorny added a comment to D66566: [lldb] Replace std::once_flag with llvm::once_flag..

Unless I'm mistaken, this is fixed by replacing std::call_once with llvm::call_once. I'll complete testing and commit it later today.

Mon, Sep 2, 10:04 PM · Restricted Project, Restricted Project
mgorny added a comment to D66566: [lldb] Replace std::once_flag with llvm::once_flag..

This broke NetBSD buildbot: http://lab.llvm.org:8011/builders/netbsd-amd64/builds/21974

Mon, Sep 2, 10:55 AM · Restricted Project, Restricted Project

Wed, Aug 28

mgorny added a comment to D66390: [PATCH] [llvm] [Support] Update license on ConvertUTF.* per upstream license change.

Ping.

Wed, Aug 28, 8:44 AM · Restricted Project

Aug 19 2019

mgorny added inline comments to D65697: [lit] Fix internal env calling env.
Aug 19 2019, 7:31 PM · Restricted Project
mgorny added a comment to D66390: [PATCH] [llvm] [Support] Update license on ConvertUTF.* per upstream license change.

As I've noted on D64740, the code in breakpad is identical (except for ordering and whitespace changes) to our initial code. All code differences between us and breakpad are our local changes. Therefore, I think we can change the license in place. If you really insist, I can reorder the functions match ordering in breakpad, and do some whitespace changes ;-).

Aug 19 2019, 10:27 AM · Restricted Project
mgorny added a comment to D64740: Use the ConvertUTF.cpp from breakpad which is under a compatible license And reintegrate our custom changes.

@sylvestre.ledru, I just went through breakpad code, comparing it with the initial code imported to clang. After reordering and aligning whitespace, the code is identical. This means that 1) the tests are failing because of regressions reintroduced by porting breakpad code, and 2) we can just change the license header because all differences in code are of our own making. Therefore, I propose that we go forward with D66390 instead of putting more time into regressing code just to fix it again.

Aug 19 2019, 10:27 AM · Restricted Project

Aug 18 2019

mgorny added a comment to D64740: Use the ConvertUTF.cpp from breakpad which is under a compatible license And reintegrate our custom changes.

Do you want me to try to take a look at the problems?

Aug 18 2019, 5:01 AM · Restricted Project
mgorny created D66390: [PATCH] [llvm] [Support] Update license on ConvertUTF.* per upstream license change.
Aug 18 2019, 3:10 AM · Restricted Project
mgorny added a comment to D64740: Use the ConvertUTF.cpp from breakpad which is under a compatible license And reintegrate our custom changes.

Actually, I think the license change can be submitted separately, so I'll do just that.

Aug 18 2019, 2:49 AM · Restricted Project
mgorny added a comment to D64740: Use the ConvertUTF.cpp from breakpad which is under a compatible license And reintegrate our custom changes.

Any chance to move this forward? I've just noticed we're missing this one license, and fixing it would render LLVM non-free in Gentoo (read: cause a massive shitstorm for some of our users). I just wanted to do a similar port and found this while looking for earlier work.

Aug 18 2019, 2:43 AM · Restricted Project

Aug 16 2019

mgorny added a comment to D65983: Autogenerate the shebang lines for tools/opt-viewer.

This looks like a correct approach to me.

Aug 16 2019, 10:22 PM · Restricted Project

Aug 3 2019

mgorny updated the diff for D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP].
Aug 3 2019, 11:39 PM
mgorny added a comment to D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP].

@jfb, could you please remove your red flag now? ;-)

Aug 3 2019, 11:19 PM

Aug 2 2019

mgorny added a comment to D64666: [Sema] Enable -Wimplicit-int-float-conversion for integral to floating point precision loss.

The warning is actually correct here. This implicit integral to float conversion loses precision. Is it the intended behavior of the code? If so, we can simply add an explicit type cast to silence the warning.

Aug 2 2019, 10:02 PM · Restricted Project, Restricted Project
mgorny updated subscribers of D64666: [Sema] Enable -Wimplicit-int-float-conversion for integral to floating point precision loss.

This change seems to have broken libc++ tests when run with trunk clang:
http://lab.llvm.org:8011/builders/netbsd-amd64/builds/21221/steps/run%20unit%20tests/logs/FAIL%3A%20libc%2B%2B%3A%3Aeval.pass.cpp
and more in http://lab.llvm.org:8011/builders/netbsd-amd64/builds/21221

Aug 2 2019, 2:23 PM · Restricted Project, Restricted Project
mgorny updated subscribers of D64908: Fix and test inter-procedural register allocation for ARM.

This change broke NetBSD buildbot:
http://lab.llvm.org:8011/builders/netbsd-amd64/builds/21240/steps/ninja%20build%20local/logs/stdio

Aug 2 2019, 2:16 PM · Restricted Project
mgorny accepted D65674: [lit] Fix 42812: lit test suite can no longer be run stand-alone.

WFM.

Aug 2 2019, 2:11 PM · Restricted Project
mgorny added inline comments to D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP].
Aug 2 2019, 10:08 AM
mgorny added inline comments to D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP].
Aug 2 2019, 7:17 AM

Aug 1 2019

mgorny added a comment to D64647: <WIP> [lldb] [Process/NetBSD] Multithread support.

Not sure if we're taking about the same thing. I meant the status in resume actions. I think it'd be logical if 'no action' meant 'resume in same state as prior to stopping the process', and explicit eStateS* meant 'keep this thread stopped after resuming'.

Aug 1 2019, 12:33 AM · Restricted Project
mgorny added inline comments to D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP].
Aug 1 2019, 12:18 AM

Jul 31 2019

mgorny added a child revision for D64647: <WIP> [lldb] [Process/NetBSD] Multithread support: D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP].
Jul 31 2019, 9:21 PM · Restricted Project
mgorny added a parent revision for D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP]: D64647: <WIP> [lldb] [Process/NetBSD] Multithread support.
Jul 31 2019, 9:21 PM
mgorny created D65555: [lldb] [Process/NetBSD] Enable reporting of new and exited threads [WIP].
Jul 31 2019, 9:21 PM
mgorny planned changes to D64647: <WIP> [lldb] [Process/NetBSD] Multithread support.

It seems that the patch is wrong with the current logic, and this is somehow blurry because of Linux implementation limitations. FWIU, eStateSuspended will never happen and instead we should keep threads without explicit action suspsended. It's unclear yet whether this is desirable long-term, or if we should change the logic to explicitly indicate state for each thread.

Jul 31 2019, 9:18 PM · Restricted Project
mgorny added a comment to D65156: [lit] Protect full test suite from FILECHECK_OPTS.

After debugging more on my system, it seems that not in front of a %{lit} causes lit's internal shell to use an external env instead of the internal env. Fine for ubuntu. Not fine for windows. Will post more later.

Jul 31 2019, 10:52 AM · Restricted Project

Jul 30 2019

mgorny added a comment to D65156: [lit] Protect full test suite from FILECHECK_OPTS.

Hmm, I suspect the problem here mostly affects people running the test suite via CMake rule rather than directly, correct? So maybe it would be more portable to clean the env via ${CMAKE_PROGRAM} -E env ....

Jul 30 2019, 7:51 PM · Restricted Project
mgorny committed rG89a214eaf10b: [lldb] [test/lldb-vscode] Use realpath to match vscode behavior (authored by mgorny).
[lldb] [test/lldb-vscode] Use realpath to match vscode behavior
Jul 30 2019, 12:48 AM
mgorny committed rG71e32aca46d1: [lldb] [test/lldb-vscode] Use os.path.dirname() [NFC] (authored by mgorny).
[lldb] [test/lldb-vscode] Use os.path.dirname() [NFC]
Jul 30 2019, 12:48 AM
mgorny committed rL367291: [lldb] [test/lldb-vscode] Use realpath to match vscode behavior.
[lldb] [test/lldb-vscode] Use realpath to match vscode behavior
Jul 30 2019, 12:47 AM
mgorny closed D65432: [lldb] [test/lldb-vscode] Use realpath to match vscode behavior.
Jul 30 2019, 12:46 AM · Restricted Project
mgorny committed rL367290: [lldb] [test/lldb-vscode] Use os.path.dirname() [NFC].
[lldb] [test/lldb-vscode] Use os.path.dirname() [NFC]
Jul 30 2019, 12:46 AM
mgorny added a comment to D65432: [lldb] [test/lldb-vscode] Use realpath to match vscode behavior.

FTR, the failure fixed by this is: http://lab.llvm.org:8011/builders/netbsd-amd64/builds/21195/steps/run%20unit%20tests/logs/FAIL%3A%20lldb-Suite%3A%3ATestVSCode_launch.py

Jul 30 2019, 12:14 AM · Restricted Project
mgorny created D65432: [lldb] [test/lldb-vscode] Use realpath to match vscode behavior.
Jul 30 2019, 12:14 AM · Restricted Project

Jul 29 2019

mgorny committed rGf9108f76fa87: [lldb] [test] Mark newly running test XFAIL on NetBSD (authored by mgorny).
[lldb] [test] Mark newly running test XFAIL on NetBSD
Jul 29 2019, 11:12 PM
mgorny committed rL367285: [lldb] [test] Mark newly running test XFAIL on NetBSD.
[lldb] [test] Mark newly running test XFAIL on NetBSD
Jul 29 2019, 11:11 PM
mgorny added a comment to D65335: [llvm] [lit/tests] Replace 'env -u' with more portable construct.

Are you talking about this *specific* change or the original change that added env usage?

Jul 29 2019, 10:17 PM · Restricted Project
mgorny committed rGe0ab4c8ee468: [lldb] [test] Mark three new tests XFAIL on NetBSD (authored by mgorny).
[lldb] [test] Mark three new tests XFAIL on NetBSD
Jul 29 2019, 7:56 AM
mgorny committed rL367228: [lldb] [test] Mark three new tests XFAIL on NetBSD.
[lldb] [test] Mark three new tests XFAIL on NetBSD
Jul 29 2019, 7:54 AM

Jul 26 2019

mgorny added a comment to D65334: [llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty.

We are using it to force verbose output on buildbot ;-).

Good to know. By the way, you'd get roughly the same output with FILECHECK_OPTS=-dump-input=fail, which is not deprecated. Adding -v or -vv will provide much more info.

Jul 26 2019, 8:53 AM · Restricted Project
mgorny committed rG40a10446c080: [llvm] [lit/tests] Replace 'env -u' with more portable construct (authored by mgorny).
[llvm] [lit/tests] Replace 'env -u' with more portable construct
Jul 26 2019, 8:40 AM
mgorny committed rGffc722a35817: [llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty (authored by mgorny).
[llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty
Jul 26 2019, 8:39 AM
mgorny committed rL367123: [llvm] [lit/tests] Replace 'env -u' with more portable construct.
[llvm] [lit/tests] Replace 'env -u' with more portable construct
Jul 26 2019, 8:39 AM
mgorny closed D65335: [llvm] [lit/tests] Replace 'env -u' with more portable construct.
Jul 26 2019, 8:39 AM · Restricted Project
mgorny committed rL367122: [llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty.
[llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty
Jul 26 2019, 8:39 AM
mgorny closed D65334: [llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty.
Jul 26 2019, 8:39 AM · Restricted Project
mgorny added a comment to D65334: [llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty.

We are using it to force verbose output on buildbot ;-). But setting to an empty value should be very uncommon. The uses I've been able to grep in LLVM all set it to 1.

Jul 26 2019, 8:28 AM · Restricted Project
mgorny added a comment to D65156: [lit] Protect full test suite from FILECHECK_OPTS.

This change broke NetBSD buildbots, e.g.: http://lab.llvm.org:8011/builders/netbsd-amd64/builds/21152/steps/run%20unit%20tests/logs/FAIL%3A%20lit%3A%3A%20googletest-upstream-format.py

Jul 26 2019, 7:11 AM · Restricted Project
mgorny added a parent revision for D65335: [llvm] [lit/tests] Replace 'env -u' with more portable construct: D65334: [llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty.
Jul 26 2019, 7:11 AM · Restricted Project
mgorny added a child revision for D65334: [llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty: D65335: [llvm] [lit/tests] Replace 'env -u' with more portable construct.
Jul 26 2019, 7:11 AM · Restricted Project
mgorny created D65335: [llvm] [lit/tests] Replace 'env -u' with more portable construct.
Jul 26 2019, 7:11 AM · Restricted Project
mgorny created D65334: [llvm] [FileCheck] Use FILECHECK_DUMP_INPUT_ON_FAILURE only when non-empty.
Jul 26 2019, 7:05 AM · Restricted Project

Jul 25 2019

mgorny committed rGe1c159e86ac2: [lldb] [Process/NetBSD] Report stopped process on SIGSTOP (authored by mgorny).
[lldb] [Process/NetBSD] Report stopped process on SIGSTOP
Jul 25 2019, 1:28 PM
mgorny committed rL367047: [lldb] [Process/NetBSD] Report stopped process on SIGSTOP.
[lldb] [Process/NetBSD] Report stopped process on SIGSTOP
Jul 25 2019, 1:27 PM
mgorny closed D65289: [lldb] [Process/NetBSD] Report stopped process on SIGSTOP.
Jul 25 2019, 1:27 PM · Restricted Project, Restricted Project
mgorny updated the diff for D65289: [lldb] [Process/NetBSD] Report stopped process on SIGSTOP.

Two more apparent XPASS-es.

Jul 25 2019, 10:35 AM · Restricted Project, Restricted Project