Contribute
Register

[TOOL] [Generate Proper Problem Reporting Files]

Status
Not open for further replies.
Thanks solved
 
black.dragon74 said:
Last update: 04 Mar 2018
Current Version: 4.2

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.

Updates 4.1 to 4.2:
  • Experimental support for Chameleon (and similar) boot-loaders.
  • Check for ACPI origin files age. Should not be older than 1 day.
Updates 3.2 to 4.0:
  • Fix potential user's file deletion loophole
  • Make IOREG dump dynamic (time values are adjusted automatically for slower machines)
  • Include generic IOREG dump if normal IOREG dump fails more than 3 times.
  • Handle scenarios where CLOVER might not be installed.
  • Include kernel panic logs if exits.
  • Fixed issues with whitespaces in EFI pathname.
  • If root elevations fails, exit.
  • Include list of all loaded kexts in dump.
Update 3.1 - 1 Jan 2018:
  • Mask MLB in RtVariables section of config.plist
  • Fixed STDERR for pledit
Update 3.0 - 29 Dec 2017:
  • Fix conflicts with GNU date on some developer environments (Fix kernel log generation)
Update 2.9 - 21 Dec 2017:
  • Fix kextcache output redunancy on 10.13.1+
Update 2.8 - 13 Dec 2017:
  • Add NVRAM dump functionality.
  • Fix broken update functionality when using "-u" arg.
Update 2.7 - 12 Dec 2017:
  • If a new update for the script it available, it will update automatically. (Helps to stay you up-to-date)
  • New IOReg dump mechanism for slow machines.
  • Include script version in the dump report.
Update 2.6 - 11 Dec 2017:
  • IOREG dump will never ever fail again.
Update 2.5 - 3 Dec 2017:
  • Check for IORegistryExplorer version 2.1
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
Click to expand...
Amazing ! :clap::clap::clap::clap:
 
Great , thanks for your work . This make all more easy ,thanks thanks thanks.!!
 
Come with the errors:
Found script data directory at /Users/you/Library/debugNk
EFI Mount Script (RehabMan) not found. Need to fetch it.
Checking connectivity..
Unable to connect to the internet. Aborted.

It looks like something need to be downloaded. And my networks are fine. Can I download the files needed manually to skip the step? Or is there a list of all files needed?
 
face1203 said:
Come with the errors:
Found script data directory at /Users/you/Library/debugNk
EFI Mount Script (RehabMan) not found. Need to fetch it.
Checking connectivity..
Unable to connect to the internet. Aborted.

It looks like something need to be downloaded. And my networks are fine. Can I download the files needed manually to skip the step? Or is there a list of all files needed?
Click to expand...

Look at the code for checkConn:
Code: 
function checkConn(){
    if ping -c 1 $testURL &>/dev/null;
        then
        echo "Internet connectivity is all good to go."
    else
        echo "Unable to connect to the internet. Aborted."
        exit
    fi
}

$testURL expands to google:
Code: 
testURL="google.com"

So it is testing the result of pinging google:
Code: 
ping -c 1 google.com
 
Hi Black and rehab

I bought wifi adapter TP-Link WN881ND ARtheros 9827
i followed several guide and it is still not detected

Rehabman pointed to run Debug to find out the problem

So I downloaded install_tool.sh
run and type chmod a+x ~/Downloads/install_tools.sh
~/Downloads/install_tools.sh

and I'm getting asf
Dumping loaded ACPI tables.
Dumped loaded ACPI tables.
Dumping System log.
Dumping kernel log.
Dumping kextstat.
Dumping kextcache
Dumping clover files.
Mounted EFI at /Volumes/EFI (credits RehabMan)
Verifying your EFI files...
You forgot to press F4 or Fn+F4 at clover boot screen.
Please reboot and press F4 or Fn+F4 to dump ACPI origin files.
Unmounted /Volumes/EFI

You forgot to press F4 or Fn+F4 at clover boot screen(clover GUI).
by pressing F4 on clover boot screen the extracted files should be in EFI/CLOVER/ACPI/origin/

by clover boot screen do you mean at the selection of boot drive as attached?
I pressed f4 and in does not show any thing I'm not sure if this worked.
is it supposed to show something after i press f4?

Im not familiar with computer codes and im a noob
please guide me
 

Attachments

  • tonymacx86 clover.jpg
    tonymacx86 clover.jpg
    45.1 KB · Views: 164
amuse.me said:
Hi Black and rehab

I bought wifi adapter TP-Link WN881ND ARtheros 9827
i followed several guide and it is still not detected

Rehabman pointed to run Debug to find out the problem

So I downloaded install_tool.sh
run and type chmod a+x ~/Downloads/install_tools.sh
~/Downloads/install_tools.sh

and I'm getting asf
Dumping loaded ACPI tables.
Dumped loaded ACPI tables.
Dumping System log.
Dumping kernel log.
Dumping kextstat.
Dumping kextcache
Dumping clover files.
Mounted EFI at /Volumes/EFI (credits RehabMan)
Verifying your EFI files...
You forgot to press F4 or Fn+F4 at clover boot screen.
Please reboot and press F4 or Fn+F4 to dump ACPI origin files.
Unmounted /Volumes/EFI

You forgot to press F4 or Fn+F4 at clover boot screen(clover GUI).
by pressing F4 on clover boot screen the extracted files should be in EFI/CLOVER/ACPI/origin/

by clover boot screen do you mean at the selection of boot drive as attached?
I pressed f4 and in does not show any thing I'm not sure if this worked.
is it supposed to show something after i press f4?

Im not familiar with computer codes and im a noob
please guide me
Click to expand...
you won't see anything happen when you press f4 f2 on the clover boot screen, that is normal, after pressing, reboot then re run the tool again
 
On Mohave gen_debug always giving an ioreg dumb failed error. I give a permission on Privacy tab for IORegisterExplorer.app but it didn't change anything? Still giving the same error? How to past this error?
 
Last edited:
telepati said:
On Mohave gen_debug always giving an ioreg dumb failed error. I give a permission on Privacy tab for IORegisterExplorer.app but it didn't change anything? Still giving the same error? How to past this error?
Click to expand...
I will push an update when I upgrade to mojave
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top