[lldb-dev] dosep.py is not running any tests on MacOSX...

2015-08-11 Thread Greg Clayton via lldb-dev
Anyone know what is up? It runs all tests in 30 seconds and says they all 
passed, but nothing is actually being run...
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] dosep.py is not running any tests on MacOSX...

2015-08-11 Thread Greg Clayton via lldb-dev
Never mind, I had DebugSymbols enabled and was getting this for a test that was 
run:

% /usr/bin/python /Volumes/work/gclayton/Documents/src/lldb/tot/test/dotest.py 
-s 2015-08-11-14_11_36 -p TestPublicAPIHeaders.py 
/Volumes/work/gclayton/Documents/src/lldb/tot/test/api/check_public_api_headers
defaults read com.apple.DebugSymbols =>
{
DBGFileMappedPaths = (
"/Library/Caches/com.apple.bni.symbols/*.apple.com/uuids",
"/Library/Caches/com.apple.bni.symbols/*.apple.com/uuids"
);
DBGSpotlightPaths = (
);
}

Disable automatic lookup and caching of dSYMs before running the test suite!
Exiting...

The detest.py needs to return an error for this case and it needs to be caught 
by dosep.py...


> On Aug 11, 2015, at 2:03 PM, Greg Clayton via lldb-dev 
>  wrote:
> 
> Anyone know what is up? It runs all tests in 30 seconds and says they all 
> passed, but nothing is actually being run...
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] dosep.py is not running any tests on MacOSX...

2015-08-11 Thread Zachary Turner via lldb-dev
Whew, I had checked in something yesterday that I was worried might have
broken something, so I was frantically doing a rebuild to see if it was me.

Side question: This isn't the first time I've seen you call it "detest".
Do you really hate it that much, or is it just a common typo?  :)

On Tue, Aug 11, 2015 at 2:15 PM Greg Clayton via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> Never mind, I had DebugSymbols enabled and was getting this for a test
> that was run:
>
> % /usr/bin/python
> /Volumes/work/gclayton/Documents/src/lldb/tot/test/dotest.py -s
> 2015-08-11-14_11_36 -p TestPublicAPIHeaders.py
> /Volumes/work/gclayton/Documents/src/lldb/tot/test/api/check_public_api_headers
> defaults read com.apple.DebugSymbols =>
> {
> DBGFileMappedPaths = (
> "/Library/Caches/com.apple.bni.symbols/*.apple.com/uuids",
> "/Library/Caches/com.apple.bni.symbols/*.apple.com/uuids"
> );
> DBGSpotlightPaths = (
> );
> }
>
> Disable automatic lookup and caching of dSYMs before running the test
> suite!
> Exiting...
>
> The detest.py needs to return an error for this case and it needs to be
> caught by dosep.py...
>
>
> > On Aug 11, 2015, at 2:03 PM, Greg Clayton via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> >
> > Anyone know what is up? It runs all tests in 30 seconds and says they
> all passed, but nothing is actually being run...
> > ___
> > lldb-dev mailing list
> > lldb-dev@lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] dosep.py is not running any tests on MacOSX...

2015-08-11 Thread Jim Ingham via lldb-dev

> On Aug 11, 2015, at 2:19 PM, Zachary Turner via lldb-dev 
>  wrote:
> 
> Whew, I had checked in something yesterday that I was worried might have 
> broken something, so I was frantically doing a rebuild to see if it was me.
> 
> Side question: This isn't the first time I've seen you call it "detest".  Do 
> you really hate it that much, or is it just a common typo?  :)
> 

That's what spell check turns dotest into.

Jim


> On Tue, Aug 11, 2015 at 2:15 PM Greg Clayton via lldb-dev 
>  wrote:
> Never mind, I had DebugSymbols enabled and was getting this for a test that 
> was run:
> 
> % /usr/bin/python 
> /Volumes/work/gclayton/Documents/src/lldb/tot/test/dotest.py -s 
> 2015-08-11-14_11_36 -p TestPublicAPIHeaders.py 
> /Volumes/work/gclayton/Documents/src/lldb/tot/test/api/check_public_api_headers
> defaults read com.apple.DebugSymbols =>
> {
> DBGFileMappedPaths = (
> "/Library/Caches/com.apple.bni.symbols/*.apple.com/uuids",
> "/Library/Caches/com.apple.bni.symbols/*.apple.com/uuids"
> );
> DBGSpotlightPaths = (
> );
> }
> 
> Disable automatic lookup and caching of dSYMs before running the test suite!
> Exiting...
> 
> The detest.py needs to return an error for this case and it needs to be 
> caught by dosep.py...
> 
> 
> > On Aug 11, 2015, at 2:03 PM, Greg Clayton via lldb-dev 
> >  wrote:
> >
> > Anyone know what is up? It runs all tests in 30 seconds and says they all 
> > passed, but nothing is actually being run...
> > ___
> > lldb-dev mailing list
> > lldb-dev@lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
> 
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] [3.7 Release] Release Candidate 2 available

2015-08-11 Thread Hans Wennborg via lldb-dev
Hello everyone,

Source, binaries and docs for LLVM 3.7.0-rc2 are now available at
http://llvm.org/pre-releases/3.7.0/

Please try them out, run tests, build your favourite projects, and
*file bugs* reporting any issues that you find.

We are now getting into the part of the release process where it's
time to wrap things up, so if you were thinking about doing some tests
or getting something fixed before the release, this is the time.

Thanks,
Hans
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] DNBConfig and debugserver

2015-08-11 Thread Bruce Mitchener via lldb-dev
Hello!

This is probably for the Apple People since it relates to debugserver...

I was going to fix an issue with the cmake build on Mac OS X related to the
mig generation step and DNBConfig.h, but when I started digging into
things, I noticed that DNBConfig.h isn't needed any longer.

The only test that it performs is for whether or not 64 bit Mach exceptions
can be used.

The code that actually handled non-64 bit Mach exceptions was removed in
2011 by this commit:

commit 0e8147bd867e4cdaae9400f56d02c7aacd40a9b3
Author: Greg Clayton 
Date:   Fri Oct 28 22:59:14 2011 +

Enabled the "printf" attribute on all debugserver logging functions and
fixed
the ensuing mayhem.



git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@143244
91177308-0d34-0410-b5e6-96231b3b80d8


So, I'm wondering what the right next step is:


   - Just fix the issue that I was going to fix in the cmake build system.
   - Remove the unused test for 64 bit Mach exception handling and that
   usage of DNBConfig.h
   - Remove DNBConfig.h entirely along with the machinery for generating it
   since nothing actually needs or uses it.
   - Something else.

I'm happy to do any of the above options.

Cheers,

 - Bruce

PS. HavAVX.s is missing an EOL at EOF, and so it generates a warning. Can I
just commit an EOL at EOF without going through Phabricator? That won't
break anything, right?
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] DNBConfig and debugserver

2015-08-11 Thread Bruce Mitchener via lldb-dev
Just in case the below came out with a resolution of "Let's remove it", I
submitted this for review:

http://reviews.llvm.org/D11971

 - Bruce

On Wed, Aug 12, 2015 at 11:21 AM, Bruce Mitchener  wrote:

> Hello!
>
> This is probably for the Apple People since it relates to debugserver...
>
> I was going to fix an issue with the cmake build on Mac OS X related to
> the mig generation step and DNBConfig.h, but when I started digging into
> things, I noticed that DNBConfig.h isn't needed any longer.
>
> The only test that it performs is for whether or not 64 bit Mach
> exceptions can be used.
>
> The code that actually handled non-64 bit Mach exceptions was removed in
> 2011 by this commit:
>
> commit 0e8147bd867e4cdaae9400f56d02c7aacd40a9b3
> Author: Greg Clayton 
> Date:   Fri Oct 28 22:59:14 2011 +
>
> Enabled the "printf" attribute on all debugserver logging functions
> and fixed
> the ensuing mayhem.
>
>
>
> git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@143244
> 91177308-0d34-0410-b5e6-96231b3b80d8
>
>
> So, I'm wondering what the right next step is:
>
>
>- Just fix the issue that I was going to fix in the cmake build system.
>- Remove the unused test for 64 bit Mach exception handling and that
>usage of DNBConfig.h
>- Remove DNBConfig.h entirely along with the machinery for generating
>it since nothing actually needs or uses it.
>- Something else.
>
> I'm happy to do any of the above options.
>
> Cheers,
>
>  - Bruce
>
> PS. HavAVX.s is missing an EOL at EOF, and so it generates a warning. Can
> I just commit an EOL at EOF without going through Phabricator? That won't
> break anything, right?
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev