[lldb-dev] Problems when testing
filcab+lldb-dev at gmail.com
Fri Nov 2 14:12:47 PDT 2012
But shouldn't Xcode say anything?
I followed all the (weird) steps in the doc, but I will try again.
On Fri, Nov 2, 2012 at 2:07 PM, Greg Clayton <gclayton at apple.com> wrote:
> On Nov 2, 2012, at 1:43 PM, "Malea, Daniel" <daniel.malea at intel.com>
> > 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.
> > Dan
> > 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
> >> 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.
> >> Regards,
> >> Filipe
> >> _______________________________________________
> >> lldb-dev mailing list
> >> lldb-dev at cs.uiuc.edu
> >> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
> > _______________________________________________
> > lldb-dev mailing list
> > lldb-dev at cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev