Use XDebug on a Devilbox with PhpStorm and Postman Host OS. Tested on: openSUSE 15.1 Leap; Fedora 30; Ubuntu 18.04.3 LTS; Pop!OS 19.10 (might apply to most recent Ubuntu derivates). Postman Canary Be the first to experience new Postman features. If you want to be first in line to experience new features, download our latest Canary builds available for OSX (x64) / Windows (x86 or x64) / Linux (x86 or x64) for a sneak peek. Our Canary builds are designed for early adopters, and may sometimes break. Download Postman Canary.
Xdebug Postman App
Besides interactive debugging, PhpStorm integration with Xdebug also supports profiling. PhpStorm provides visual representation of profiling data generated by Xdebug. You can select several snapshots at a time and collect the aggregated profiling information.
Before profiling with Xdebug, download, install and configure the components of the PHP development environment. Normally, these are a PHP engine, a web server, and the Xdebug tool.
Enable profiling with Xdebug
Configure Xdebug
Download and install the Xdebug tool.
Integrate Xdebug with the PHP engine.
Integrate Xdebug with PhpStorm.
Enable the Xdebug profiler
Open the active php.ini file in the editor:
In the Settings/Preferences dialog Ctrl+Alt+S, click PHP.
On the PHP page that opens, click next to the CLI Interpreter field.
In the CLI Interpreters dialog that opens, the Configuration file read-only field shows the path to the active php.ini file. Click Open in Editor.
Do one of the following:
To permanently enable the profiler, set the xdebug.profiler_enable (for Xdebug 2) or xdebug.mode (for Xdebug 3) directive:
To enable triggering the profiler from the browser by using the
XDEBUG_PROFILEcookie or a GET/POST parameter, set the following directives depending on the Xdebug version used:Guitar pro 7 no sound. Make sure that you selected your Bluetooth peripheral from the Guitar Pro 7 Audio/MIDI preferences. Access the Guitar Pro 7 Audio/MIDI preferences from the File or Guitar Pro 7 menu. If your playback is garbled and distorted: Windows: Select None as Audio Input. MacOS: Select Built in Mic as Audio input. The playback is poor or distorted? Access the Guitar Pro 7 Audio/MIDI preferences from the File or Guitar Pro 7.
xdebug.profiler_enable = 0; xdebug.profiler_enable_trigger = 1;xdebug.mode = profile; xdebug.start_with_request = trigger;
Configure the way to toggle the profiler from the browser
Xdebug Docker Phpstorm Postman
To specify the XDEBUG_PROFILE cookie or a GET/POST parameter, do one of the following:
Xdebug Phpstorm Postman
Specify the values manually.
- Generate the bookmarklets to toggle the debugger through. These bookmarklets will appear on the toolbar of your browser. They provide control over the debugger cookie, through them you will activate and deactivate the debugger.
Enable the Bookmarks toolbar in your browser by doing one of the following depending on the browser type:
In Firefox, choose View | Toolbar | Bookmarks Toolbar.
In Chrome, choose Bookmarks | Show bookmarks bar.
In the Settings/Preferences dialog Ctrl+Alt+S, navigate to PHP | Debug.
On the Debug page, that opens, click the Use debugger bookmarklets to initiate debugger from your favorite browser link.
On the Zend Debugger & Xdebug bookmarklets page that opens, check the debugging engine settings and click Generate. The bookmarks for listed debugging-related actions are generated.
Drag the generated links to the bookmark toolbar in your browser.
Use XDebug on a Devilbox with PhpStorm and Postman Host OS. Tested on: openSUSE 15.1 Leap; Fedora 30; Ubuntu 18.04.3 LTS; Pop!OS 19.10 (might apply to most recent Ubuntu derivates). Postman Canary Be the first to experience new Postman features. If you want to be first in line to experience new features, download our latest Canary builds available for OSX (x64) / Windows (x86 or x64) / Linux (x86 or x64) for a sneak peek. Our Canary builds are designed for early adopters, and may sometimes break. Download Postman Canary.
Xdebug Postman App
Besides interactive debugging, PhpStorm integration with Xdebug also supports profiling. PhpStorm provides visual representation of profiling data generated by Xdebug. You can select several snapshots at a time and collect the aggregated profiling information.
Before profiling with Xdebug, download, install and configure the components of the PHP development environment. Normally, these are a PHP engine, a web server, and the Xdebug tool.
Enable profiling with Xdebug
Configure Xdebug
Download and install the Xdebug tool.
Integrate Xdebug with the PHP engine.
Integrate Xdebug with PhpStorm.
Enable the Xdebug profiler
Open the active php.ini file in the editor:
In the Settings/Preferences dialog Ctrl+Alt+S, click PHP.
On the PHP page that opens, click next to the CLI Interpreter field.
In the CLI Interpreters dialog that opens, the Configuration file read-only field shows the path to the active php.ini file. Click Open in Editor.
Do one of the following:
To permanently enable the profiler, set the xdebug.profiler_enable (for Xdebug 2) or xdebug.mode (for Xdebug 3) directive:
To enable triggering the profiler from the browser by using the
XDEBUG_PROFILEcookie or a GET/POST parameter, set the following directives depending on the Xdebug version used:Guitar pro 7 no sound. Make sure that you selected your Bluetooth peripheral from the Guitar Pro 7 Audio/MIDI preferences. Access the Guitar Pro 7 Audio/MIDI preferences from the File or Guitar Pro 7 menu. If your playback is garbled and distorted: Windows: Select None as Audio Input. MacOS: Select Built in Mic as Audio input. The playback is poor or distorted? Access the Guitar Pro 7 Audio/MIDI preferences from the File or Guitar Pro 7.
xdebug.profiler_enable = 0; xdebug.profiler_enable_trigger = 1;xdebug.mode = profile; xdebug.start_with_request = trigger;
Configure the way to toggle the profiler from the browser
Xdebug Docker Phpstorm Postman
To specify the XDEBUG_PROFILE cookie or a GET/POST parameter, do one of the following:
Xdebug Phpstorm Postman
Specify the values manually.
- Generate the bookmarklets to toggle the debugger through. These bookmarklets will appear on the toolbar of your browser. They provide control over the debugger cookie, through them you will activate and deactivate the debugger.
Enable the Bookmarks toolbar in your browser by doing one of the following depending on the browser type:
In Firefox, choose View | Toolbar | Bookmarks Toolbar.
In Chrome, choose Bookmarks | Show bookmarks bar.
In the Settings/Preferences dialog Ctrl+Alt+S, navigate to PHP | Debug.
On the Debug page, that opens, click the Use debugger bookmarklets to initiate debugger from your favorite browser link.
On the Zend Debugger & Xdebug bookmarklets page that opens, check the debugging engine settings and click Generate. The bookmarks for listed debugging-related actions are generated.
Drag the generated links to the bookmark toolbar in your browser.
Specify the location for storing accumulated profiling data
Open the active php.ini file in the editor:
In the Settings/Preferences dialog Ctrl+Alt+S, click PHP.
On the PHP page that opens, click next to the CLI Interpreter field.
In the CLI Interpreters dialog that opens, the Configuration file read-only field shows the path to the active php.ini file. Click Open in Editor.
Define location for accumulating profiling snapshots by specifying the xdebug.profiler_output_dir (for Xdebug 2) or xdebug.output_dir (for Xdebug 3) directive.
xdebug.profiler_output_dir = ''Specify the name of the file to store snapshots in through the value of the
xdebug.profiler_output_namedirective. The default name is cachegrind.out.%p, where%pis the name format specifier. Accept the default name or define a custom one in compliance with the following standard:The name should always be cachegrind.out.
Use the supported format specifiers.
Analyze Xdebug profiling data
When integration with Xdebug profiler is enabled, PhpStorm provides visual representation of profiler snapshots. PhpStorm opens a separate editor tab with four views where the data are presented based on different criteria.
Initiate an Xdebug debugging session
Do one of the following:
To start debugging an entire application, create debug configuration of the type PHP Web Page, and launch debugging by clicking .
See Debug with a PHP web page debug configuration for details.
To debug a specific PHP HTTP request, define a debug configuration of the type PHP HTTP Request, and launch debugging by clicking .
See Debug a PHP HTTP request for details.
To initiate a zero-configuration debugging session:
Toggle the Start Listen PHP Debug Connections button on the PhpStorm toolbar so that it changes to . After that PhpStorm starts listening to the port of the debugging engine used in the current project. Debugging ports are set at the PhpStorm level on the PHP | Debug page of the Settings/Preferences dialog Ctrl+Alt+S.
Open the starting page of your application in the browser, choose the Start debugger bookmark to activate the debugging engine from the browser, re-load the current page (the starting page of the application), and then return to PhpStorm.
Xdebug Postman
Retrieve the data accumulated by the profiler
Xdebug Debug Postman
From the main menu, choose Tools | Analyze Xdebug Profiler Snapshot.
In the Select Xdebug profiler snapshot dialog, that opens, choose the folder and the file where the profiling data is stored.
PhpStorm presents the collected profiling data in a separate editor tab with the name of the selected profiler output file.
Examine the profiling data
Xdebug Postman Extension
When you request on the accumulated profiling data, PhpStorm opens its visualized presentation in a separate editor tab. The tab is named after the selected profiler output file and consists of several views. Switch between the views to analyze the profiling data based on various criteria of analysis.
In the Execution Statistics view, examine the summary information about execution metrics of every called function.
In the Call Tree view, explore the execution paths of all called functions.
To explore the execution paths of a specific function, select the function in the Call Tree view and view its callees in the Callees view.
To explore all the paths that can result in calling a specific function, select the function in the Call Tree view and examine its possible callers in the Callers view.
