Contribute
Register

[TOOL] [Generate Proper Problem Reporting Files]

Status
Not open for further replies.
Joined
Jul 11, 2014
Messages
436
Motherboard
Asus A555LAB
CPU
i3-4005U
Graphics
HD 4400
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
I think something in the script is causing all files collected from EFI/Clover to have the same timestamp.
As a result, it is impossible tell the relative age of the files in ACPI/patched vs. ACPI/origin.
Fixed. Thanks for reporting! This error was because I never thought of using timestamp to compare files. And, if we use cp it sets the timestamp value to that of when the command was executed.

If running gen_debug ver2.1+ update using
Code:
gen_debug -u

Regards
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
184,624
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS

Thanks.

This error was because I never thought of using timestamp to compare files.

I'm not using a timestamp to compare files.
But I do use the timestamps to determine whether I should bother.
If the user forgot to press F4, then I won't bother comparing them (no sense in comparing against old files), and will instead request they read "Problem Reporting" more carefully :)
 
Joined
Jul 11, 2014
Messages
436
Motherboard
Asus A555LAB
CPU
i3-4005U
Graphics
HD 4400
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
But I do use the timestamps to determine whether I should bother.
If the user forgot to press F4, then I won't bother comparing them (no sense in comparing against old files), and will instead request they read "Problem Reporting" more carefully :)
Totally agreed.
 
Joined
Apr 6, 2017
Messages
80
Motherboard
gigabyte GA-Z170X-UD5 TH (Clover)
CPU
i7 6700K
Graphics
Gigabyte GTX 1050 TI
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
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

Wow. So helpful for me. Being a newbie to this scene I have definitely been one of those responsible for wasting so much of everyones valuable time. Thanks for your patience. This is a great tool. Makes my life and hopefully those of the moderators that much easier. Thanks again.
 
Joined
Oct 11, 2017
Messages
74
Motherboard
Lenovo 510s-14isk (OpenCore UEFI)
CPU
i5-6257u
Graphics
Iris 550, 1920x1080
Hi, the script doesn't check if the correct version of ioreg is installed. Please correct it if you can for best user experience.
Thanks
 
Joined
Jul 11, 2014
Messages
436
Motherboard
Asus A555LAB
CPU
i3-4005U
Graphics
HD 4400
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hi, the script doesn't check if the correct version of ioreg is installed. Please correct it if you can for best user experience.
Thanks
Good idea. Thanks.
 
Joined
Jul 11, 2014
Messages
436
Motherboard
Asus A555LAB
CPU
i3-4005U
Graphics
HD 4400
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Hi, the script doesn't check if the correct version of ioreg is installed. Please correct it if you can for best user experience.
Thanks
Implemented. Update using gen_debug -u (Check OP)

Regards
 
Last edited:

RehabMan

Moderator
Joined
May 3, 2012
Messages
184,624
Motherboard
Intel DH67BL
CPU
i7-2600K
Graphics
HD 3000
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Regarding a feature in Clover to automatically force preboot.log and ACPI/origin capture, I should have time after the holidays to implement it.

Thinking about it, it will definitely be enabled via a config.plist setting, and not NVRAM (because the user may not have working NVRAM...)

I've noticed a few reports coming back with wrong ioreg (collected with wrong IORegistryExplorer.app). Is this because they have IORegistryExplorer.app v3.x installed, or do they have an old script... or can that be corrected for in the script (eg. download IORegistryExplorer v2.1 if they have the wrong version installed).
 
Joined
Jul 11, 2014
Messages
436
Motherboard
Asus A555LAB
CPU
i3-4005U
Graphics
HD 4400
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
Regarding a feature in Clover to automatically force preboot.log and ACPI/origin capture, I should have time after the holidays to implement it.
That would be great!

Is this because they have IORegistryExplorer.app v3.x installed, or do they have an old script...
They have old version of script. Version 2.5 and above check for IORegistryExplorer2.1. If a wrong version is found, correct version is downloaded automatically.

P.S: Version 2.7 and above check and update script automatically if a new version is available. Unfortunately the versions prior to that need to be updated manually. User can use the script in post #1 or if running version 2.1+ he can update using “gen_debug -u” arg.

Note: “-u” arg can still be used on version 2.7+ (just in case) but there would rarely be need of it.

Regards
 
Last edited:
Status
Not open for further replies.
Top