Menu ▾ ▴

Home

OSX Service (1) crash log (1) symbolize (1) symbolicate (1) symbol DB (1)
Hofi

What's Useful Mac Services?

UMS is a collection of Mac OS X Services. Services are contextual workflows available throughout Mac OS X. They accept text or files from the current application or the Finder and appear in the Services menu. They can be used to shorten repetitive tasks f.e on files or folders.

Currently selectable service component(s)

  • Release Notes
    This file, will be copied into ~/Documents/UMS/Release Notes.rtf and opened at the end of the installation process if selected
  • Symbolize service menu
    Symbolize service menu items are simple service wrappers around symbolizelog, symbolizealllogs and add2symbolpath scripts (together with symbolizehelpers helper scripts) that can be used to symbolize OS X crash logs, hang, stall or sample files. Scripts will be copied into ~/Library/Scripts/ and the service workflow will be installed to the default location ~/Library/Services/ during installation if selected.
    You can also easily build and use a symbol DB for symbolication via Symbolize services.
  • Symbolize documentation (~/Documents/UMS/)
    Detailed documentation of Symbolize service menu, will be copied into ~/Documents/UMS/Symbolize Manual.rtf during installation if selected. Read the manual
  • Copy Paths service menu
    Copy Paths add ability to copy full path, directory name or file name parts of the selected finder items to the clipboard.
  • Mail Creation Services
    Mail Creation add ability to create mail with attachments (from the currently selected files/directories) or mail with currently selected text as message body, both via the default mailer of the current user.

Installation Instructions

UMS distributed in a Mac OS X .dmg format, simply mount it by double clicking on UMS Install 1.2.7.dmg file and than start UMS Install.app, select components you wish to install than confirm installation of each selected service component.

Changelog

Dec 2, 2013 Version 1.2.7

  • Symbolize Services
    • Added support of searching multiple paths for symbols
    • Added support of using spotlight to search for symbols

Nov 28, 2013 Version 1.2.6

  • Symbolize Services
    • Corrected identifier and identifier lines parsing and symbol file matching

Nov 23, 2013 Version 1.2.5

  • Symbolize Services
    • Corrected identifier lines parsing
    • Corrected handling of process names contains spaces
    • Added *.sample to searched file patterns in directories to symbolize

Nov 18, 2013 Version 1.2.4

  • Symbolize Services
    • Added LOG_FILE_PATTERNS, KEEP_FAILED_SYMBOLIZE_RESULTS and CONFIRM_SUCCESS options to config
    • Corrected pattern matching handling both in symbolizealllogs and add2symbolpath
    • Corrected handling of hang files where process identifier and process name could be mixed in Binary Images section and inside the log lines
  • Mail Creation Services
    • Corrected handling of multiple files selection to attach

Nov 11, 2013 Version 1.2.3

  • Symbolize Services
    • add2symbolpath script should accept file parameters too (archives can be passed directly)

Nov 7, 2013 Version 1.2.2

  • Symbolize Services
    • Fixed Identifier lines parsing from Binary Images list
    • Documentation corrected

Nov 5, 2013 Version 1.2.1

  • Symbolize Services
    • Added Symbolize Selection service

Oct 16, 2013 Version 1.2.0

  • Symbolize Services
    • Added support of Symbol Servers and Symbol Server Caches
  • Mail Creation Services
    • Added initial release

Aug 13, 2013 Version 1.1.7

  • Symbolize Services
    • Added support of 10.9.x cpu and wakeups resource spin files

Jun 28, 2013 Version 1.1.6

  • Symbolize Services
    • Removing symbolize scripts temp files after finished run
  • Copy Paths Services
    • Added initial release

Feb 27, 2013 Version 1.1.5

  • Symbolize Services
    • Corrected parsing of process names contain spaces
    • Corrected handling files with \r\n line ending that could lead to a broken final awk symbolize script file

Nov 28, 2012 Version 1.1.4

  • Symbolize Services
    • Corrected handling of 10.7.x hang files

Nov 27, 2012 Version 1.1.3

  • Symbolize Services
    • Corrected handling of 10.8.x hang files

Oct 31, 2012 Version 1.1.2

  • Symbolize Services
    • Added support of 10.6.x (Report version 7) type of sample files

Sep 11, 2012 Version 1.1.1

  • Symbolize Services
    • Initial release

Known Issues

  • symbolizing ppc standalone binaries with embedded debug symbols could not work on none ppc systems because atos could not handle those debug symbols on none ppc machines
  • some kind of logs (like 10.5, 10.6 samples) has no information at all about the examined process except the name of it, for symbolization to have a chance to work in that case you must store the matching dSYM files and/or binaries with debug info of the process in the directory of the log file itself
  • false symbolization result may happen
    • if architecture can not be detected from the log and if the process is an unibin target and the log belongs to an other architecture than the first one otool finds in the binary (the first version used as architecture during the symbolization if architecture cannot be detected and not specified explicitly)
    • if load address can not be detected from the log and the binary was loaded at a different address then the default of the architecture (f.e. the process loaded an a system using ASLR)
  • some kind of logs (like. armv7 and 10.9) does not mark the main and loaded modules with (+) prefix anymore in the Binary Images list at the end of the log files (why Apple???), so only the main module will be symbolized by default in that kind of logs (or the first one appears in the list if the main executable can not be guessed)

Bug Reporting 

Send your bug reports to ums.bugs@gmail.com

Project Admins:
MongoDB Logo MongoDB