title: Strange PHP .ini inclusion in CLI vs Built-in server
body: <p>My current config: 
  - MacOS Mojave
  - PHP 7.3.5 installed via Homebrew
  - XDebug 2.7.2 installed via PECL
  - get_loaded_extensions() in both CLI and built-in server is enabled</p>
  
  <p>While trying to configure XDebug on Mac I came across a strange problem.
  When calling </p>
  
  <pre><code>$ php --ini
  </code></pre>
  
  <p>I get</p>
  
  <pre><code>Configuration File (php.ini) Path: /usr/local/etc/php/7.3
  Loaded Configuration File:         /usr/local/etc/php/7.3/php.ini
  Scan for additional .ini files in: /usr/local/etc/php/7.3/conf.d
  Additional .ini files parsed:      /usr/local/etc/php/7.3/conf.d/ext-opcache.ini,
  /usr/local/etc/php/7.3/conf.d/ext-xdebug.ini
  </code></pre>
  
  <p>whereas calling </p>
  
  <pre><code>print php_ini_scanned_files();
  </code></pre>
  
  <p>in the script executed via built-in PHP server yields</p>
  
  <pre><code>/usr/local/etc/php/7.3/conf.d/ext-opcache.ini
  </code></pre>
  
  <p>Web server does not include my <code>xdebug</code> config, therefore there is no way to set <code>xdebug.remote_enable=1</code> option properly.</p>
  
  <p>What is even "better" is that editing <code>/usr/local/etc/php/7.3/php.ini</code> to cause parsing errors gives no warnings whatsoever.</p>
  
  <p>I'm puzzled. Does anyone has any idea what's the reason behind this?</p>