Re: Indexing broken for one project

[Alex Zavatone via Cocoa-dev]

In my work MacBook on Monterey 12.1, /private is read only, but /tmp still is 
writeable.  I just create a folder there as a test.

That aside, if there’s anything I’ve learned in the week or two since I’ve been 
using Xcode, it’s “don’t do what it doesn’t expect you to do”.  That includes 
to using the default location for derived data, which is 
~/Library/Developer/Xcode/DerivedData.

Just my wild assed guess & inclination.  

Cheers,
Alex Zavatone


> On Feb 14, 2022, at 7:29 AM, Gabriel Zachmann via Cocoa-dev 
>  wrote:
> 
> 
>> 
>> In Monterey, /tmp is now only writeable by root.
> 
> It is?
> I have been storing temp files in /tmp all my life (output from all kinds of 
> programs), and did not notice a change when upgrading to Monterey.
> 
> /Users/zach% cd /tmp
> /private/tmp% ls -ld .
> drwxrwxrwt  17 root  wheel  544 Feb 14 12:00 ./
> 
> /private/tmp% ll
> total 164008
> drwxr-xr-x@ 7 zach  wheel   224B Feb 14 14:19 
> ArtSaver-hcwtwqkubldekzfijehvpaeowamp/
> drwxr-xr-x  3 zach  wheel96B Feb 13 23:02 Build/
> drwxr-xr-x  5 zach  wheel   160B Feb 13 23:02 ModuleCache.noindex/
> drwxr-xr-x  3 zach  wheel96B Feb 13 21:59 SymbolCache.noindex/
> drwxr-xr-x  3 zach  wheel96B Feb 13 21:59 XCBuildData/
> [...]
> 
> 
> Maybe, the sticky bit is new as of Monterey?
> (which would make sense, of course, but maybe it was there all the time, 
> which it should.)
> Even so, a reboot should have cleared up any permission problems in any case, 
> since a reboot deletes all files in /tmp anyways.
> 
> So, I'm still a bit in the dark as to why it now works.
> Oh well ...
> 
> 
>> It is quite possible that Xcode couldn?t write there for the indexing.
> 
> It looks like it, but I can't see why 
> 
> 
> Best regards, Gabriel
> 
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com
> 
> This email sent to z...@mac.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Gabriel Zachmann via Cocoa-dev]

>
> In Monterey, /tmp is now only writeable by root.

It is?
I have been storing temp files in /tmp all my life (output from all kinds of 
programs), and did not notice a change when upgrading to Monterey.

/Users/zach% cd /tmp
/private/tmp% ls -ld .
drwxrwxrwt  17 root  wheel  544 Feb 14 12:00 ./

/private/tmp% ll
total 164008
drwxr-xr-x@ 7 zach  wheel   224B Feb 14 14:19 
ArtSaver-hcwtwqkubldekzfijehvpaeowamp/
drwxr-xr-x  3 zach  wheel96B Feb 13 23:02 Build/
drwxr-xr-x  5 zach  wheel   160B Feb 13 23:02 ModuleCache.noindex/
drwxr-xr-x  3 zach  wheel96B Feb 13 21:59 SymbolCache.noindex/
drwxr-xr-x  3 zach  wheel96B Feb 13 21:59 XCBuildData/
[...]


Maybe, the sticky bit is new as of Monterey?
(which would make sense, of course, but maybe it was there all the time, which 
it should.)
Even so, a reboot should have cleared up any permission problems in any case, 
since a reboot deletes all files in /tmp anyways.

So, I'm still a bit in the dark as to why it now works.
Oh well ...


> It is quite possible that Xcode couldn?t write there for the indexing.

It looks like it, but I can't see why 


Best regards, Gabriel




smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Marco S Hyman via Cocoa-dev]

On Feb 13, 2022, at 4:39 PM, Jack Brindle via Cocoa-dev 
 wrote:
> 
> In Monterey, /tmp is now only writeable by root.

??? Does terminal.app have special privs?

~% ls -l /tmp
lrwxr-xr-x@ 1 root  wheel  11 Feb  6 13:22 /tmp@ -> private/tmp
~% ls -ld /private/tmp
drwxrwxrwt  23 root  wheel  736 Feb 13 17:03 /private/tmp/
~% echo foo > /tmp/foo
~% cat /tmp/foo
foo
~% 


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Alex Zavatone via Cocoa-dev]

> On Feb 13, 2022, at 4:09 PM, Gabriel Zachmann  wrote:
> 
> The Derived Data directory is set to /tmp (i have had that setting for years).

Oh, don’t do that. 

Glad you’ve got it fixed.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Jack Brindle via Cocoa-dev]

In Monterey, /tmp is now only writeable by root. It is quite possible that 
Xcode couldn’t write there for the indexing.

When you changed to a new account, it probably changed where the derived data 
went.

It used to be that /tmp was writeable by anyone. That change bit me recently as 
well. Security?

Jack


> On Feb 13, 2022, at 4:09 PM, Gabriel Zachmann via Cocoa-dev 
>  wrote:
> 
>> This seems to indicate an error somewhere in the Xcode prefs.
> 
> Oh, wow, maybe I have resolved the issue!
> 
> The Derived Data directory is set to /tmp (i have had that setting for years).
> 
> Now, in Xcode / Preferences / Locations / Derived Data / Advanced,
> I set Custom = Relative to Derived Data.
> (Before , it was set to Absolute.)
> I have no idea, why it would not do the indexing before, and exactly what the 
> setting "Absolute" means, 
> but it looks like now it's working! 
> 
> Thanks a million to you all!
> 
> Best regards, Gabriel
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/jackbrindle%40me.com
> 
> This email sent to jackbrin...@me.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Gabriel Zachmann via Cocoa-dev]

> This seems to indicate an error somewhere in the Xcode prefs.

Oh, wow, maybe I have resolved the issue!

The Derived Data directory is set to /tmp (i have had that setting for years).

Now, in Xcode / Preferences / Locations / Derived Data / Advanced,
I set Custom = Relative to Derived Data.
(Before , it was set to Absolute.)
I have no idea, why it would not do the indexing before, and exactly what the 
setting "Absolute" means,
but it looks like now it's working!

Thanks a million to you all!

Best regards, Gabriel



smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Alex Zavatone via Cocoa-dev]

This seems to indicate an error somewhere in the Xcode prefs.

Try using it in that new user is aways am option.

Or copy the project back into another folder and see if the original user can 
open the project from the other folder.

Just the two guesses I have at the moment.

Cheers,
Alex Zavatone


> On Feb 13, 2022, at 3:07 PM, Gabriel Zachmann  wrote:
> 
> This is, indeed, strange.
> 
> I tried it, as you suggested, with a new user account on the very same 
> machine.
> Everything works just fine in a copy of the project under that pristine 
> account.
> Even when I launch the .xcodeproject in my real home, the indexing works.
> 
> It just does not work in my home.
> 
> Just now, I have tried a few other things.
> I deleted some folders in ~/Library/Deverlopers (caches, log files, devices).
> Interestingly, there is no ~/Library/Deverloper/Xcode/DerivedData! (which 
> should contain the indexing stuff; and, naturally, 
> ~pristine/Library/Developer/Xcode does contain the DerivedData).
> I have also rebooted.
> I also deleted project.xcworkspace .
> All to no avail.
> 
> So, what now? what can I do?
> 
> Stymied, Gabriel.
> 

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Ben Kennedy via Cocoa-dev]

On 13 Feb 2022, at 1:07 pm, Gabriel Zachmann via Cocoa-dev 
 wrote:

> Just now, I have tried a few other things.
> I deleted some folders in ~/Library/Deverlopers (caches, log files, devices).
> Interestingly, there is no ~/Library/Deverloper/Xcode/DerivedData! (which 
> should contain the indexing stuff; and, naturally, 
> ~pristine/Library/Developer/Xcode does contain the DerivedData).

The derived data location is an Xcode preference (under the Locations tab), so 
it follows that it would have that default value under the new user account -- 
but perhaps it's set to something different for your main user?

-ben

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Gabriel Zachmann via Cocoa-dev]

>
> Sort of straw-grasping I would try with Xcode under these circumstances?
>
> Try changing the target CPU/OS setting to something else, build, and see if 
> the indexing works.
>
> If it does, make the minimal changes needed to appropriately build your 
> target.
>

Thanks a lot for the straw , alas, it didn't work.
I changed all kinds of things, to no avail.
In other projects,  I get the indexing progress circle just fine.
in the problem project, I get it for a second, then it goes away and I get the 
crash messages in the report navigator.





smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Gabriel Zachmann via Cocoa-dev]

This is, indeed, strange.

I tried it, as you suggested, with a new user account on the very same machine.
Everything works just fine in a copy of the project under that pristine account.
Even when I launch the .xcodeproject in my real home, the indexing works.

It just does not work in my home.

Just now, I have tried a few other things.
I deleted some folders in ~/Library/Deverlopers (caches, log files, devices).
Interestingly, there is no ~/Library/Deverloper/Xcode/DerivedData! (which 
should contain the indexing stuff; and, naturally, 
~pristine/Library/Developer/Xcode does contain the DerivedData).
I have also rebooted.
I also deleted project.xcworkspace .
All to no avail.

So, what now? what can I do?

Stymied, Gabriel.



smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Kirk Kerekes via Cocoa-dev]

Sort of straw-grasping I would try with Xcode under these circumstances…

Try changing the target CPU/OS setting to something else, build, and see if the 
indexing works. 

If it does, make the minimal changes needed to appropriately build your target. 

If it doesn’t, discard straw. 

Kirk Kerekes 
(iPhone)
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Alex Zavatone via Cocoa-dev]

Here’s an idea.  Create a new user on your Mac.  Open the project from that new 
user and see if it indexes.

It worked fine on my Mac

Good luck.

> On Feb 12, 2022, at 8:24 AM, Gabriel Zachmann via Cocoa-dev 
>  wrote:
> 
> Here is another attempt at getting to the root of the indexer problem I am 
> experiencing.
> 
> First of all, thanks a lot for your helpful hints, albeit they did not 
> resolve the issue.
> 
> Here is - for recap - the description in a nutshell of my original post:
> 
> 
> A few weeks ago, indexing in Xcode 13 stopped working for one of my 
> projects.
> So, for instance, "Jump to Definition" does not work any more.
> I don't know what stopped indexing to work.
> 
> 
> I have now tried executing the command you can find in the log window of 
> Xcode (Report Navigator),
> which leads to all the crashes.
> (Below, you can find the command for my case.)
> 
> The output in the shell was this:
> clang: error: unable to execute command: Segmentation fault: 11
> clang: error: clang frontend command failed due to signal (use -v to see 
> invocation)
> Apple clang version 13.0.0 (clang-1300.0.29.30)
> Target: x86_64-apple-macos10.14
> Thread model: posix
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> clang: error: unable to execute command: Segmentation fault: 11
> clang: note: diagnostic msg: Error generating preprocessed source(s).
> 
> So, I issued the command again with -v, which revealed the "invocation".
> (See below that invocation command.)
> 
> Issuing that clang command produced just this error message:
> 
> clang -cc1 version 13.0.0 (clang-1300.0.29.30) default target 
> x86_64-apple-darwin21.2.0
> Segmentation fault
> 
> 
> So, I am nowhere closer to the root of the problem.
> 
> 
> Does anyone have an idea, how i might get more information?
> 
> 
> Best regards, Gabriel
> 
> 
> 
> 
> Encl.:
> 
> Orig. clang command as reported in the Report Navigator:
> 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
>  -x objective-c -target x86_64-apple-macos10.14 -fmessage-length=0 
> -fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=gnu11 
> -fobjc-arc -fobjc-weak -fmodules 
> -fmodules-cache-path=/tmp/ModuleCache.noindex -fmodules-prune-interval=86400 
> -fmodules-prune-after=345600 -Wnon-modular-include-in-framework-module 
> -Werror=non-modular-include-in-framework-module -Wno-trigraphs 
> -fpascal-strings -O0 -fno-common -Wno-missing-field-initializers 
> -Wno-missing-prototypes -Werror=return-type -Wdocumentation 
> -Wunreachable-code -Wno-implicit-atomic-properties 
> -Werror=deprecated-objc-isa-usage -Wno-objc-interface-ivars 
> -Werror=objc-root-class -Wno-arc-repeated-use-of-weak -Wimplicit-retain-self 
> -Wduplicate-method-match -Wno-missing-braces -Wparentheses -Wswitch 
> -Wunused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable 
> -Wunused-value -Wempty-body -Wuninitialized -Wconditional-uninitialized 
> -Wno-unknown-pragmas -Wshadow -Wno-four-char-constants -Wconversion 
> -Wconstant-conversion -Wint-conversion -Wbool-conversion -Wenum-conversion 
> -Wfloat-conversion -Wnon-literal-null-conversion -Wobjc-literal-conversion 
> -Wsign-compare -Wshorten-64-to-32 -Wpointer-sign -Wno-newline-eof 
> -Wno-selector -Wno-strict-selector-match -Wundeclared-selector 
> -Wdeprecated-implementations -DDEBUG=1 -DDEBUG=1 -DSTAND_ALONE_APP=1 
> -DOBJC_OLD_DISPATCH_PROTOTYPES=0 -isysroot 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk
>  -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -g 
> -Wno-sign-conversion -Winfinite-recursion -Wcomma 
> -Wblock-capture-autoreleasing -Wstrict-prototypes 
> -Wno-semicolon-before-method-body -Wunguarded-availability -index-store-path 
> /tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/DataStore -iquote 
> /tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/ArtSaverApp-generated-files.hmap
>  
> -I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/ArtSaverApp-own-target-headers.hmap
>  
> -I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/ArtSaverApp-all-target-headers.hmap
>  -iquote 
> /tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/ArtSaverApp-project-headers.hmap
>  
> -I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Products/Debug/include
>  
> -I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/DerivedSources-normal/x86_64
>  
> -I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/DerivedSources/x86_64
>  
> -I/tmp/Art

Re: Indexing broken for one project

[Gabriel Zachmann via Cocoa-dev]

Here is another attempt at getting to the root of the indexer problem I am 
experiencing.

First of all, thanks a lot for your helpful hints, albeit they did not resolve 
the issue.

Here is - for recap - the description in a nutshell of my original post:


 A few weeks ago, indexing in Xcode 13 stopped working for one of my 
 projects.
 So, for instance, "Jump to Definition" does not work any more.
 I don't know what stopped indexing to work.


I have now tried executing the command you can find in the log window of Xcode 
(Report Navigator),
which leads to all the crashes.
(Below, you can find the command for my case.)

The output in the shell was this:
clang: error: unable to execute command: Segmentation fault: 11
clang: error: clang frontend command failed due to signal (use -v to see 
invocation)
Apple clang version 13.0.0 (clang-1300.0.29.30)
Target: x86_64-apple-macos10.14
Thread model: posix
InstalledDir: 
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
clang: error: unable to execute command: Segmentation fault: 11
clang: note: diagnostic msg: Error generating preprocessed source(s).

So, I issued the command again with -v, which revealed the "invocation".
(See below that invocation command.)

Issuing that clang command produced just this error message:

clang -cc1 version 13.0.0 (clang-1300.0.29.30) default target 
x86_64-apple-darwin21.2.0
Segmentation fault


So, I am nowhere closer to the root of the problem.


Does anyone have an idea, how i might get more information?


Best regards, Gabriel




Encl.:

Orig. clang command as reported in the Report Navigator:

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang
 -x objective-c -target x86_64-apple-macos10.14 -fmessage-length=0 
-fdiagnostics-show-note-include-stack -fmacro-backtrace-limit=0 -std=gnu11 
-fobjc-arc -fobjc-weak -fmodules -fmodules-cache-path=/tmp/ModuleCache.noindex 
-fmodules-prune-interval†400 -fmodules-prune-after45600 
-Wnon-modular-include-in-framework-module 
-Werror=non-modular-include-in-framework-module -Wno-trigraphs -fpascal-strings 
-O0 -fno-common -Wno-missing-field-initializers -Wno-missing-prototypes 
-Werror=return-type -Wdocumentation -Wunreachable-code 
-Wno-implicit-atomic-properties -WerrorÞprecated-objc-isa-usage 
-Wno-objc-interface-ivars -Werror=objc-root-class -Wno-arc-repeated-use-of-weak 
-Wimplicit-retain-self -Wduplicate-method-match -Wno-missing-braces 
-Wparentheses -Wswitch -Wunused-function -Wno-unused-label 
-Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body 
-Wuninitialized -Wconditional-uninitialized -Wno-unknown-pragmas -Wshadow 
-Wno-four-char-constants -Wconversion -Wconstant-conversion -Wint-conversion 
-Wbool-conversion -Wenum-conversion -Wfloat-conversion 
-Wnon-literal-null-conversion -Wobjc-literal-conversion -Wsign-compare 
-Wshorten-64-to-32 -Wpointer-sign -Wno-newline-eof -Wno-selector 
-Wno-strict-selector-match -Wundeclared-selector -Wdeprecated-implementations 
-DDEBUG=1 -DDEBUG=1 -DSTAND_ALONE_APP=1 -DOBJC_OLD_DISPATCH_PROTOTYPES=0 
-isysroot 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.1.sdk
 -fasm-blocks -fstrict-aliasing -Wprotocol -Wdeprecated-declarations -g 
-Wno-sign-conversion -Winfinite-recursion -Wcomma -Wblock-capture-autoreleasing 
-Wstrict-prototypes -Wno-semicolon-before-method-body -Wunguarded-availability 
-index-store-path /tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/DataStore 
-iquote 
/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/ArtSaverApp-generated-files.hmap
 
-I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/ArtSaverApp-own-target-headers.hmap
 
-I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/ArtSaverApp-all-target-headers.hmap
 -iquote 
/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/ArtSaverApp-project-headers.hmap
 
-I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Products/Debug/include 
-I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/DerivedSources-normal/x86_64
 
-I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/DerivedSources/x86_64
 
-I/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Intermediates.noindex/ArtSaver.build/Debug/ArtSaverApp.build/DerivedSources
 -F/tmp/ArtSaver-hcwtwqkubldekzfijehvpaeowamp/Index/Build/Products/Debug 
-fsyntax-only /Users/zach/Code/ArtSaver/ArtSaverApp/AppDelegate.m -o 
/tmp/ArtSaver.build/Debug/ArtSaverApp.build/Objects-normal/x86_64/AppDelegate.o 
-Xclang -fallow-pcm-with-compiler-errors -ivfsoverlay 
/tmp/ArtSaver-hcwtwqkubl

Re: Indexing broken for one project

[Gabriel Zachmann via Cocoa-dev]

> I have come across issues where a code syntax error messes up indexing—are 
> you able to do a full, successful compilation?

Yes, I think so.

Have done Product / Clean Build Folder ,
then quit Xcode, then launched again.
The project builds fine, no warnings.

But I still have a hunch it's in the source code.
I just have no idea how to pinpoint the place.

> Other than that, I have heard that some issues might require a system 
> restart, i.e. 1) quitting Xcode; 2) deleting derived data (if you use a 
> shared location you might also want to delete or move derived data from other 
> projects); and 3) restarting the computer.

I have just tried that , still no luck.

Best regards, Gabriel



smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Keary Suska via Cocoa-dev]

I have come across issues where a code syntax error messes up indexing—are you 
able to do a full, successful compilation? Other than that, I have heard that 
some issues might require a system restart, i.e. 1) quitting Xcode; 2) deleting 
derived data (if you use a shared location you might also want to delete or 
move derived data from other projects); and 3) restarting the computer.

HTH,

Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business”



> On Feb 6, 2022, at 9:32 AM, Gabriel Zachmann via Cocoa-dev 
>  wrote:
> 
> Thanks a lot for your response.
> 
> I had tried that already, to no avail.
> 
> I am seeing lots of   "Crash detected during compilation"
> in Xcode's indexing log.
> 
> Best regards, Gabriel
> 
> 
> 
>> On 6. Feb 2022, at 19:18, Rob Petrovec  wrote:
>> 
>> Quit Xcode, delete the DerivedData directory for your project and re-open 
>> your project.  That should trigger a re-index and a full rebuild of your 
>> product.
>> 
>> The default location for the DerivedData directory is in 
>> ~/Library/Developer/Xcode/DerivedData/-> letters>.  You can also configure it to be in your source directory, like I 
>> do, so you can keep your build products with your code.
>> 
>> Hope that helps.
>> 
>> —Rob
>> 
>> 
>>> On Feb 6, 2022, at 6:20 AM, Gabriel Zachmann via Cocoa-dev 
>>>  wrote:
>>> 
>>> A few weeks ago, indexing in Xcode 13 stopped working for one of my 
>>> projects.
>>> So, for instance, "Jump to Definition" does not work any more.
>>> I don't know what stopped indexing to work.
>>> 
>>> The project consists of objective-c source code.
>>> For other projects, indexing still works fine.
>>> 
>>> I have tried to delete Derived Data (which, in my case, is stored under 
>>> /tmp).
>>> I have also tried to follow these instructions 
>>> https://levelup.gitconnected.com/uncovering-xcode-indexing-8b3f3ff82551
>>> and perused the log file, but I could not see any error messages.
>>> 
>>> Any ideas what else I can try?
>>> Could it be something in the source code / header files?
>>> (The project compiles just fine, though.)
>>> 
>>> Best regards, Gabriel
>>> 
>>> ___
>>> 
>>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>>> 
>>> Please do not post admin requests or moderator comments to the list.
>>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>>> 
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com
>>> 
>>> This email sent to petr...@mac.com
>> 
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/cocoa-dev%40esoteritech.com
> 
> This email sent to cocoa-...@esoteritech.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Gabriel Zachmann via Cocoa-dev]

Thanks a lot for your response.

I had tried that already, to no avail.

I am seeing lots of   "Crash detected during compilation"
in Xcode's indexing log.

Best regards, Gabriel



> On 6. Feb 2022, at 19:18, Rob Petrovec  wrote:
>
> Quit Xcode, delete the DerivedData directory for your project and re-open 
> your project.  That should trigger a re-index and a full rebuild of your 
> product.
>
> The default location for the DerivedData directory is in 
> ~/Library/Developer/Xcode/DerivedData/- letters>.  You can also configure it to be in your source directory, like I 
> do, so you can keep your build products with your code.
>
> Hope that helps.
>
> —Rob
>
>
>> On Feb 6, 2022, at 6:20 AM, Gabriel Zachmann via Cocoa-dev 
>>  wrote:
>>
>> A few weeks ago, indexing in Xcode 13 stopped working for one of my projects.
>> So, for instance, "Jump to Definition" does not work any more.
>> I don't know what stopped indexing to work.
>>
>> The project consists of objective-c source code.
>> For other projects, indexing still works fine.
>>
>> I have tried to delete Derived Data (which, in my case, is stored under 
>> /tmp).
>> I have also tried to follow these instructions
>>  https://levelup.gitconnected.com/uncovering-xcode-indexing-8b3f3ff82551
>> and perused the log file, but I could not see any error messages.
>>
>> Any ideas what else I can try?
>> Could it be something in the source code / header files?
>> (The project compiles just fine, though.)
>>
>> Best regards, Gabriel
>>
>> ___
>>
>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>>
>> Please do not post admin requests or moderator comments to the list.
>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>>
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com
>>
>> This email sent to petr...@mac.com
>



smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Alex Zavatone via Cocoa-dev]

Over several weeks, I’ve had the most annoying problem with Xcode and pods with 
the sandbox always being out of sync.  

Guess what fixed it?  Quitting and restarting Xcode.  Sometimes this product 
just reminds you of Windows 3.1.

Best of luck.

Gabriel want me to try your project out in Xcode 13?

Let me know.

Cheers,
Alex Zavatone


> On Feb 6, 2022, at 12:18 PM, Rob Petrovec via Cocoa-dev 
>  wrote:
> 
> Quit Xcode, delete the DerivedData directory for your project and re-open 
> your project.  That should trigger a re-index and a full rebuild of your 
> product.
> 
> The default location for the DerivedData directory is in 
> ~/Library/Developer/Xcode/DerivedData/- letters>.  You can also configure it to be in your source directory, like I 
> do, so you can keep your build products with your code.
> 
> Hope that helps.
> 
> —Rob
> 
> 
>> On Feb 6, 2022, at 6:20 AM, Gabriel Zachmann via Cocoa-dev 
>> mailto:cocoa-dev@lists.apple.com>> wrote:
>> 
>> A few weeks ago, indexing in Xcode 13 stopped working for one of my projects.
>> So, for instance, "Jump to Definition" does not work any more.
>> I don't know what stopped indexing to work.
>> 
>> The project consists of objective-c source code.
>> For other projects, indexing still works fine.
>> 
>> I have tried to delete Derived Data (which, in my case, is stored under 
>> /tmp).
>> I have also tried to follow these instructions 
>> https://levelup.gitconnected.com/uncovering-xcode-indexing-8b3f3ff82551
>> and perused the log file, but I could not see any error messages.
>> 
>> Any ideas what else I can try?
>> Could it be something in the source code / header files?
>> (The project compiles just fine, though.)
>> 
>> Best regards, Gabriel
>> 
>> ___
>> 
>> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>> 
>> Please do not post admin requests or moderator comments to the list.
>> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>> 
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com 
>> 
>> 
>> This email sent to petr...@mac.com 
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com 
> )
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com 
> 
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com 
> 
> 
> This email sent to z...@mac.com 
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Indexing broken for one project

[Rob Petrovec via Cocoa-dev]

Quit Xcode, delete the DerivedData directory for your project and re-open your 
project.  That should trigger a re-index and a full rebuild of your product.

The default location for the DerivedData directory is in 
~/Library/Developer/Xcode/DerivedData/-.  You can also configure it to be in your source directory, like I do, 
so you can keep your build products with your code.

Hope that helps.

—Rob


> On Feb 6, 2022, at 6:20 AM, Gabriel Zachmann via Cocoa-dev 
>  wrote:
> 
> A few weeks ago, indexing in Xcode 13 stopped working for one of my projects.
> So, for instance, "Jump to Definition" does not work any more.
> I don't know what stopped indexing to work.
> 
> The project consists of objective-c source code.
> For other projects, indexing still works fine.
> 
> I have tried to delete Derived Data (which, in my case, is stored under /tmp).
> I have also tried to follow these instructions 
>  https://levelup.gitconnected.com/uncovering-xcode-indexing-8b3f3ff82551
> and perused the log file, but I could not see any error messages.
> 
> Any ideas what else I can try?
> Could it be something in the source code / header files?
> (The project compiles just fine, though.)
> 
> Best regards, Gabriel
> 
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/petrock%40mac.com
> 
> This email sent to petr...@mac.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Indexing broken for one project

[Gabriel Zachmann via Cocoa-dev]

PS:
I have also done this
   defaults write com.apple.dt.Xcode IDEIndexShowLog -bool YES

Now, in the indexing log I can see in Xcode, there are a lot of messages
   "Crash detected during compilation".
But I still don't get a clue as to what might be causing this.





smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Indexing broken for one project

[Gabriel Zachmann via Cocoa-dev]

A few weeks ago, indexing in Xcode 13 stopped working for one of my projects.
So, for instance, "Jump to Definition" does not work any more.
I don't know what stopped indexing to work.

The project consists of objective-c source code.
For other projects, indexing still works fine.

I have tried to delete Derived Data (which, in my case, is stored under /tmp).
I have also tried to follow these instructions
  https://levelup.gitconnected.com/uncovering-xcode-indexing-8b3f3ff82551
and perused the log file, but I could not see any error messages.

Any ideas what else I can try?
Could it be something in the source code / header files?
(The project compiles just fine, though.)

Best regards, Gabriel



smime.p7s
Description: S/MIME cryptographic signature
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com