Databases
StackOverflow2013
Postsdbo
POHow do I redirect all errors, including uncaught exceptions, NSLog calls, and other logs, to a log file on Mac OS X?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I redirect all errors, including uncaught exceptions, NSLog calls, and other logs, to a log file on Mac OS X?
    primarykey
    data
    text
    <p>I am attempting to find a logging framework for a Cocoa application, written in ObjC.</p> <p>What I've attempted so far:</p> <ol> <li>Use NSLog, but then realise that it is very hard to configure and redirect. I suppose I could hack it and write a macro that obtains the information I want, such as thread ID, current function, current line, current file, current time, the message, etcetera, and then uses NSLog, however...</li> <li>NSLog ultimately uses NSLogv, which ultimately uses asl, so I thought "fantastic", I tried using asl instead, with the default client and context (If I was doing this properly, I would've had to create a new client for each thread), however, unless I create a macro, this is also very verbose, and I noticed that the logs sent via asl got broadcast system wide, whereas NSLog only logged to stderr, and I want them to both go to the same log!</li> <li>I then noticed that errors, are formatted in a different way (different datestamp, etc), so there is now a third logging context.</li> </ol> <p>What l logging framework setup can I use to have ALL messages logged through that framework in a convenient fashion so that if there is a problem with an application, a developer can get the log files, and figure out what went wrong?</p> <p>I don't want to simply redirect stderr, I want to have a structured log output that contains all of the logs. I don't want some logs going to standard output, I don't want any logs sent to a syslogd, I just want all the logs written to a single file, that reliably identifies all the pertinent information about that log message (such as thread ID, message, the function that called the logger, etcetera), in format that is easy to view and visualise.</p> <p>What I want is to redirect all current logs to the new destination.</p> <p>Does anyone have any suggestions?</p> <p>EDIT:</p> <p>Effectively, what I want to do, in ObjC terms is:</p> <ol> <li>Do "method swizzling" on the NSLog function. Is this possible? Is it possible to (re)configure the use of the Apple System Logger to override any prior configuration of the service within the same application?</li> <li>Determine all the places where I have to catch unhandled exceptions. THis includes, but possibly isn't limited to: Unhandled Cocoa Exceptions. Unhandled ObjC exceptions. Unhandled C++ exceptions. Unix Signals.</li> <li>Catch and log the stack for errors such as those raised by CoreGraphics. (The ones that simply log a message saying "Add a breakpoint using your debugger!!!").</li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USArafangion
    1. USArafangion
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow do I redirect all errors, including uncaught exceptions, NSLog calls, and other logs, to a log file on Mac OS X?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow do I redirect all errors, including uncaught exceptions, NSLog calls, and other logs, to a log file on Mac OS X?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow do I redirect all errors, including uncaught exceptions, NSLog calls, and other logs, to a log file on Mac OS X?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload