FROM : Gerd Knops
DATE : Sun Nov 25 00:05:18 2007
On Nov 24, 2007, at 4:39 PM, Gerd Knops wrote:
>
> On Nov 24, 2007, at 2:41 PM, Gerd Knops wrote:
>
>> Seems the old trick
>>
>> freopen([logPath fileSystemRepresentation],"a",stderr);
>>
>> to catch NSLog output no longer works under Leopard. It catches
>> anything written to stderr, but no NSLog output. Any ideas?
>>
> The point at which the above is executed is crucial. main() is to
> early, so is +load. Seems to work if done in [NSApplication init].
>
Sorry, misdiagnosed that one. It is rather more obscure:
If logPath is on a local disk, NSLog and output directed to stderr
appear in logPath.
However if logPath is inside an NFS-mounted home directory, only stder
output appears, but NSLog output goes missing. When exactly the
freopen happens doesn't matter.
Gerd
DATE : Sun Nov 25 00:05:18 2007
On Nov 24, 2007, at 4:39 PM, Gerd Knops wrote:
>
> On Nov 24, 2007, at 2:41 PM, Gerd Knops wrote:
>
>> Seems the old trick
>>
>> freopen([logPath fileSystemRepresentation],"a",stderr);
>>
>> to catch NSLog output no longer works under Leopard. It catches
>> anything written to stderr, but no NSLog output. Any ideas?
>>
> The point at which the above is executed is crucial. main() is to
> early, so is +load. Seems to work if done in [NSApplication init].
>
Sorry, misdiagnosed that one. It is rather more obscure:
If logPath is on a local disk, NSLog and output directed to stderr
appear in logPath.
However if logPath is inside an NFS-mounted home directory, only stder
output appears, but NSLog output goes missing. When exactly the
freopen happens doesn't matter.
Gerd
| Related mails | Author | Date |
|---|---|---|
| Gerd Knops | Nov 24, 21:41 | |
| Gerd Knops | Nov 24, 23:39 | |
| Gerd Knops | Nov 25, 00:05 |






Cocoa mail archive

