|
Xcode 11.2.1, macOS Mojave 10.14.6, ObjC
This morning Xcode decided to stifle all NSLogs in _one_ of my macOS development apps. printfs and fprintf(stderr,*) still get written to the Xcode debug window. NSLogs do not. They don't even go to the system console.
I set a symbolic breakpoint at NSLog, and it does break there, in assembler.
Other projects work normally! I've restarted Xcode, and even rebooted the machine. No joy. Is there perhaps some hidden Xcode build setting to ignore NSLogs?
How can I get Xcode to once again write NSLogs to the debug window?
-Carl
|
|
|
Carl,
I found that the new logging system does not like it when you target something like 10.9 or prior… i was loosing NSLog statements on some apps until I moved the deployment target to 10.11 or 10.12… Might this be affecting you?
Sandor
toggle quoted messageShow quoted text
On Jul 29, 2020, at 15:43, Carl Hoefs <newslists@autonomy.caltech.edu> wrote:
Xcode 11.2.1, macOS Mojave 10.14.6, ObjC
This morning Xcode decided to stifle all NSLogs in _one_ of my macOS development apps. printfs and fprintf(stderr,*) still get written to the Xcode debug window. NSLogs do not. They don't even go to the system console.
I set a symbolic breakpoint at NSLog, and it does break there, in assembler.
Other projects work normally! I've restarted Xcode, and even rebooted the machine. No joy. Is there perhaps some hidden Xcode build setting to ignore NSLogs?
How can I get Xcode to once again write NSLogs to the debug window?
-Carl
|
|
|
Sandor,
Thanks for the suggestion.
My "macOS Deployment Target" is set to "macOS 10.14" for both Debug and Release. Trying other versions gives the same result.
-Carl
toggle quoted messageShow quoted text
On Jul 29, 2020, at 12:48 PM, Sandor Szatmari <admin.szatmari.net@gmail.com> wrote:
Carl,
I found that the new logging system does not like it when you target something like 10.9 or prior… i was loosing NSLog statements on some apps until I moved the deployment target to 10.11 or 10.12… Might this be affecting you?
Sandor
On Jul 29, 2020, at 15:43, Carl Hoefs <newslists@autonomy.caltech.edu> wrote:
Xcode 11.2.1, macOS Mojave 10.14.6, ObjC
This morning Xcode decided to stifle all NSLogs in _one_ of my macOS development apps. printfs and fprintf(stderr,*) still get written to the Xcode debug window. NSLogs do not. They don't even go to the system console.
I set a symbolic breakpoint at NSLog, and it does break there, in assembler.
Other projects work normally! I've restarted Xcode, and even rebooted the machine. No joy. Is there perhaps some hidden Xcode build setting to ignore NSLogs?
How can I get Xcode to once again write NSLogs to the debug window?
-Carl
|
|
|
FWIW, I just upgraded to Xcode 11.3.1. Same issue.
-Carl
Sandor,Thanks for the suggestion.My "macOS Deployment Target" is set to "macOS 10.14" for both Debug and Release. Trying other versions gives the same result.-CarlOn Jul 29, 2020, at 12:48 PM, Sandor Szatmari <admin.szatmari.net@...> wrote:
Carl,
I found that the new logging system does not like it when you target something like 10.9 or prior… i was loosing NSLog statements on some apps until I moved the deployment target to 10.11 or 10.12… Might this be affecting you?
Sandor
On Jul 29, 2020, at 15:43, Carl Hoefs <newslists@...> wrote:
Xcode 11.2.1, macOS Mojave 10.14.6, ObjC
This morning Xcode decided to stifle all NSLogs in _one_ of my macOS development apps. printfs and fprintf(stderr,*) still get written to the Xcode debug window. NSLogs do not. They don't even go to the system console.
I set a symbolic breakpoint at NSLog, and it does break there, in assembler.
Other projects work normally! I've restarted Xcode, and even rebooted the machine. No joy. Is there perhaps some hidden Xcode build setting to ignore NSLogs?
How can I get Xcode to once again write NSLogs to the debug window?
-Carl
|
|
|
Verify you’ve not enabled OS_ACTIVITY_MODE. -- Gary L. Wade http://www.garywade.com/
On Jul 29, 2020, at 1:55 PM, Carl Hoefs <newslists@...> wrote:
FWIW, I just upgraded to Xcode 11.3.1. Same issue.
-Carl
Sandor,Thanks for the suggestion.My "macOS Deployment Target" is set to "macOS 10.14" for both Debug and Release. Trying other versions gives the same result.-CarlOn Jul 29, 2020, at 12:48 PM, Sandor Szatmari <admin.szatmari.net@...> wrote:
Carl,
I found that the new logging system does not like it when you target something like 10.9 or prior… i was loosing NSLog statements on some apps until I moved the deployment target to 10.11 or 10.12… Might this be affecting you?
Sandor
On Jul 29, 2020, at 15:43, Carl Hoefs <newslists@...> wrote:
Xcode 11.2.1, macOS Mojave 10.14.6, ObjC
This morning Xcode decided to stifle all NSLogs in _one_ of my macOS development apps. printfs and fprintf(stderr,*) still get written to the Xcode debug window. NSLogs do not. They don't even go to the system console.
I set a symbolic breakpoint at NSLog, and it does break there, in assembler.
Other projects work normally! I've restarted Xcode, and even rebooted the machine. No joy. Is there perhaps some hidden Xcode build setting to ignore NSLogs?
How can I get Xcode to once again write NSLogs to the debug window?
-Carl
|
|
|
Bingo!
I have no idea what OS_ACTIVITY_MODE is or why it was disabled.
On Jul 29, 2020, at 2:32 PM, Gary L. Wade < garywade@...> wrote:
Verify you’ve not enabled OS_ACTIVITY_MODE. FWIW, I just upgraded to Xcode 11.3.1. Same issue.
-Carl
Sandor,Thanks for the suggestion.My "macOS Deployment Target" is set to "macOS 10.14" for both Debug and Release. Trying other versions gives the same result.-CarlOn Jul 29, 2020, at 12:48 PM, Sandor Szatmari <admin.szatmari.net@...> wrote:
Carl,
I found that the new logging system does not like it when you target something like 10.9 or prior… i was loosing NSLog statements on some apps until I moved the deployment target to 10.11 or 10.12… Might this be affecting you?
Sandor
On Jul 29, 2020, at 15:43, Carl Hoefs <newslists@...> wrote:
Xcode 11.2.1, macOS Mojave 10.14.6, ObjC
This morning Xcode decided to stifle all NSLogs in _one_ of my macOS development apps. printfs and fprintf(stderr,*) still get written to the Xcode debug window. NSLogs do not. They don't even go to the system console.
I set a symbolic breakpoint at NSLog, and it does break there, in assembler.
Other projects work normally! I've restarted Xcode, and even rebooted the machine. No joy. Is there perhaps some hidden Xcode build setting to ignore NSLogs?
How can I get Xcode to once again write NSLogs to the debug window?
-Carl
|
|
|
I’d never heard of this either… found this interesting…
On Jul 29, 2020, at 17:48, Carl Hoefs <newslists@...> wrote:
Bingo!
I have no idea what OS_ACTIVITY_MODE is or why it was disabled. Thanks! -Carl On Jul 29, 2020, at 2:32 PM, Gary L. Wade < garywade@...> wrote:
Verify you’ve not enabled OS_ACTIVITY_MODE. FWIW, I just upgraded to Xcode 11.3.1. Same issue.
-Carl
Sandor,Thanks for the suggestion.My "macOS Deployment Target" is set to "macOS 10.14" for both Debug and Release. Trying other versions gives the same result.-CarlOn Jul 29, 2020, at 12:48 PM, Sandor Szatmari <admin.szatmari.net@...> wrote:
Carl,
I found that the new logging system does not like it when you target something like 10.9 or prior… i was loosing NSLog statements on some apps until I moved the deployment target to 10.11 or 10.12… Might this be affecting you?
Sandor
On Jul 29, 2020, at 15:43, Carl Hoefs <newslists@...> wrote:
Xcode 11.2.1, macOS Mojave 10.14.6, ObjC
This morning Xcode decided to stifle all NSLogs in _one_ of my macOS development apps. printfs and fprintf(stderr,*) still get written to the Xcode debug window. NSLogs do not. They don't even go to the system console.
I set a symbolic breakpoint at NSLog, and it does break there, in assembler.
Other projects work normally! I've restarted Xcode, and even rebooted the machine. No joy. Is there perhaps some hidden Xcode build setting to ignore NSLogs?
How can I get Xcode to once again write NSLogs to the debug window?
-Carl
|
|
|
