It’s just a gotcha if you find that no profiling logs are being written. This shouldn’t be a problem out of the box. ![]() You may want to ensure the write permissions are set to allow Xdebug to write to “/tmp/xdebug/”. I’ve found that if you are using WinCacheGrind on Windows, the profiler output name should start with “cachegrind” instead of “callgrind” because WinCacheGrind only recognizes one type of file. Xdebug.profiler_output_dir = "/tmp/xdebug/" Xdebug.profiler_output_name = "cachegrind.out.%t-%s" See the note below about this Xdebug.profiler_enable_trigger = On Profiling activated when requested by the GET parameter Xdebug.profiler_enable = Off Profiling not activated by default Xdebug.remote_addr_header = "HTTP_X_XDEBUG_REMOTE_ADDRESS" See the bonus section at the very bottom for details on using this Select a connect-back IP from the $_SERVER value set in a custom header Xdebug.idekey = "PHPSTORM" The IDE key which should match the XDEBUG_SESSION cookie value ![]() Xdebug.remote_port = 9000 Port on the IDE to connect back to. Xdebug.remote_connect_back = On Use a special $_SERVER variable to get the remote address xdebug.remote_host = "localhost" This is unused if the next setting is 'On' Xdebug.remote_autostart = Off Only start xdebug on demand, not on every request
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |