Last update: 2 Dec 2017
Hello guys,
I have seen many instances where people start a thread with the problem they are facing on their hack.
They try to describe the issue in their own way that most of the times, is not able to properly describe what's going wrong with their system.
The developers and other members on tonymacx86 can point out the problem exactly when they have a set of files, called problem reporting files.
These are basically a set of files that contain various logs and some other components.
Many a times a normal user can not generate those files properly and it leads to a lot of wastage of good time, frustrated by this, I wrote a script to generate proper problem reporting files. You can have a look at the source code
here
The purpose of this guide is to tell the normal user on how to generate those files properly for debugging.
I wrote a script that automatically installs that debug report generator script and then gives you a .zip output.
If you are seeking help about a problem and you must attach problem reporting files as it saves a lot of time.
How to generate debug report:-
It is very simple, you just have to download the attached script and run it. The script in attachment will install the tool for you and will then prompt if you want to generate the files.
If you want to generate files next time, you just have to invoke: "gen_debug" from terminal (without quotes)
How to download and run attached script :-
- Unzip the downloaded zip file
- Open terminal
- Assuming your script is in Downloads folder, type the following code :-
Code:
chmod a+x ~/Downloads/install_tools.sh
~/Downloads/install_tools.sh
Args for gen_debug:
You can use custom set of args for controlling gen_debug output, this list will be updated as new features become available
- gen_debug -u || To update your copy (available from ver2.1+)
- gen_debug -sysprofile || To include your system profile in the dump (available from ver2.2+)
- gen_debug -sysprofile txt || To include system profile in the dump but in TXT format
Note: Whenever you change anything,
you should attach new output of gen_debug.
Note 2: It is recommended to update your copy of gen_debug every alternate month (for fixes and new features). To do so, If you are running version 2.1 or above, you can simply type "
gen_debug -u" (without quotes) in terminal. If you are running version 2.0 or less, you can use the attached installer script to update your copy.
CHANGELOGS:
Update 2.4 - 2 Dec 2017:
- Script now also dumps your boot log
Update 2.3 - 2 Dec 2017:
- Fixed an issue where the time stamp of files was overwritten to current system time, reported by RehabMan.
Update 2.2 - 27Nov 2017:
- Added option to generate system information dump using -sysprofile arg
Update 2.1 - 27Nov 2017:
- Fixed an issue where IOREG was not saved on some machines
- You can now update your copy of OSX-Debug by using "-u" arg, like gen_debug -u
Regards
