[lldb-dev] Problems when testing
gclayton at apple.com
Fri Nov 2 14:07:51 PDT 2012
On Nov 2, 2012, at 1:43 PM, "Malea, Daniel" <daniel.malea at intel.com> wrote:
> Hi Filipe,
> Yes, I am seeing the same behaviour on Mac OS X Mountain Lion (10.8.2) here, but not on Linux. It was not introduced recently, as we've been seeing the behaviour for the last month or two, and also with Lion.
> A workaround, though not a great one, is to invoke the tests with "sudo" then all the test inferior processes exit cleanly. I am not sure what the root-cause is.
It is usually your "lldb_codesign" code signing cert going bad, expired, or no longer valid due to OS upgrade/reinstall.
> On 2012-11-02, at 3:34 PM, Filipe Cabecinhas wrote:
>> Hi all,
>> I'm having some weird problems when testing lldb.
>> Most tests don't stop the a.out file and leave it in an uninterruptible sleep.
>> This will exhaust the machine's PID space and make it stop working.
>> Can you reproduce this?
>> I'm using lldb from trunk (updated a few minutes ago), and it happens the same way wether I compile it with the latest clang or clang from the latest Xcode.
>> I'm on Mountain Lion 10.8.2.
>> lldb-dev mailing list
>> lldb-dev at cs.uiuc.edu
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
More information about the lldb-dev