dupdb-admin(1) [suse man page]

dupdp-admin(1)						      General Commands Manual						    dupdp-admin(1)

NAME

       dupdb-admin - Manage the duplicate database for apport-retrace.

SYNOPSIS

       dupdb-admin -f dbpath status

       dupdb-admin -f dbpath dump

       dupdb-admin -f dbpath changeid oldid newid

DESCRIPTION

       apport-retrace(1)  has the capability of checking for duplicate bugs (amonst other things). It uses an SQLite database for keeping track of
       master bugs.  dupdb-admin is a small tool to manage that database.

       The central concept in that database is a "crash signature", a string that uniquely identifies a particular crash. It  is  built  from  the
       executable path name, the signal number or exception name, and the topmost functions of the stack trace.

       The  database maps crash signatures to the 'master' crash id and thus can close duplicate crash reports with a reference to that master ID.
       It also tracks the status of crashes (open/fixed in a particular version) to be able to identify regressions.

MODES

       status Print general status of the duplicate db. For now, it only shows the time when the database was "consolidated" last, i. e. when  the
	      bug states (open/fixed) in the SQLite database where updated to the actual states in the bug tracking system.

       dump   Print a list of all database entries.

       changeid
	      Change the associated crash ID for a particular crash.

OPTIONS

       -f path, --database-file=path
	      Instead  of processing the new crash reports in /var/crash/, report a particular report in an arbitrary file location.  This is use-
	      ful for copying a crash report to a machine with internet connection and reporting it from there. This defaults to  ~./apport_dupli-
	      cates.db.

AUTHOR

       apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>.

Martin Pitt							  August 01, 2007						    dupdp-admin(1)

ReportCrash(8)						    BSD System Manager's Manual 					    ReportCrash(8)

NAME

     ReportCrash -- Generates crash reports

SYNOPSIS

     ReportCrash

DESCRIPTION

     ReportCrash analyzes crashing processes and saves a crash report to disk.	A crash report contains information that can help a developer
     diagnose the cause of a crash.  ReportCrash also records the identity of the crashing process and the location of the saved crash report in
     the system.log and the ASL log database.

     ReportCrash is invoked automatically by launchd when a crash is detected.	For applications and other processes running in the per-user
     launchd context, ReportCrash runs as a LaunchAgent and saves crash reports in the user's ~/Library/Logs/DiagnosticReports/ directory.  For
     daemons, other processes running in the system launchd context and other privileged processes, ReportCrash runs as a LaunchDaemon and saves
     crash reports in the system's /Library/Logs/DiagnosticReports directory where they are only readable by admin users.  If there are too many
     crash reports saved for a particular process, older reports will automatically be removed in order to conserve disk space.

     launchtl can be used to disable and re-enable crash reporting.  To disable crash reporting:

	   launchctl unload -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
	   sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist

     To re-enable crash reporting:

	   launchctl load -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
	   sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist

     For application crashes (but not background process crashes) ReportCrash will display a dialog notifying the user that the application unex-
     pectedly quit and offering to reopen the application or send the report to Apple.	For developers, the behavior of this dialog can be
     adjusted using /Developer/Applications/Utilities/CrashReporterPrefs.app which is installed as part of the developer tools.

     Crash reports which are sent to Apple are submitted anonymously by the SubmitDiagInfo process.  The reports are used by Apple to improve its
     products.	Users who need support should use http://www.apple.com/support or other authorized support channels.  Developers who are ADC mem-
     bers should report bugs using http://bugreporter.apple.com in order to allow for two way communication between Apple and the bug reporter.

     More information about interpreting the contents of crash reports can be found in Technote 2123: http://developer.apple.com/tech-
     notes/tn2004/tn2123.html

SEE ALSO

     launchd(8), launchd.plist(8), launchctl(8), spindump(8), SubmitDiagInfo(8)

Mac OS								   June 1, 2019 							    Mac OS