0000087: Warning about headers when "register_shutdown_function" used - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update
0000087	Xdebug	Uncategorized	public	2004-08-11 08:25	2006-03-09 14:06

Reporter	emgie	Assigned To
Priority	normal	Severity	minor	Reproducibility	unable to reproduce
Status	closed	Resolution	reopened

Summary	0000087: Warning about headers when "register_shutdown_function" used
Description	When "register_shutdown_function" is used in the code, the following warning is issued: Warning: Cannot modify header information - headers already sent in Unknown on line 0 All goes well when xdebug.so is not used. This bug causes PEAR packages to have problems
Additional Information	PHP version is 5.0.0 stable, not -dev (can't choose such an option) Sample code: <?php function logit($x) { $f = fopen("/tmp/logit.txt", "a"); fwrite($f, "$x\n"); fclose($f); } function sayonara() { } register_shutdown_function("sayonara"); ?>
Tags	No tags attached.

Operating System	Fedora Core 1
PHP Version	4.3.0

derick 2004-08-23 08:15 administrator ~0000182	I can not reproduce this with your code, it works fine. Can you please give me a list of all xdebug related settings that show up in phpinfo() output?

emgie 2004-08-23 12:52 reporter ~0000184	xdebug xdebug support => enabled Version => 2.0.0dev Supported protocols => Revision DBGp - Common DeBuGger Protocol => $Revision: 1.55 $ GDB - GNU Debugger protocol => $Revision: 1.76 $ PHP3 - PHP 3 Debugger protocol => $Revision: 1.19 $ Directive => Local Value => Master Value xdebug.allowed_clients => no value => no value xdebug.auto_trace => Off => Off xdebug.collect_includes => On => On xdebug.collect_params => Off => Off xdebug.collect_return => Off => Off xdebug.default_enable => On => On xdebug.dump.COOKIE => no value => no value xdebug.dump.ENV => no value => no value xdebug.dump.FILES => no value => no value xdebug.dump.GET => no value => no value xdebug.dump.POST => no value => no value xdebug.dump.REQUEST => no value => no value xdebug.dump.SERVER => no value => no value xdebug.dump.SESSION => no value => no value xdebug.dump_globals => On => On xdebug.dump_once => On => On xdebug.dump_undefined => Off => Off xdebug.extended_info => On => On xdebug.idekey => maciek => whatever xdebug.manual_url => http://www.php.net => http://www.php.net xdebug.max_nesting_level => 100 => 100 xdebug.profiler_enable => Off => Off xdebug.profiler_output_dir => /tmp => /tmp xdebug.profiler_output_name => crc32 => crc32 xdebug.remote_enable => On => On xdebug.remote_handler => gdb => gdb xdebug.remote_host => localhost => localhost xdebug.remote_mode => req => req xdebug.remote_port => 9000 => 9000 xdebug.show_local_vars => Off => Off xdebug.show_mem_delta => Off => Off xdebug.trace_format => 0 => 0 xdebug.trace_options => 0 => 0 xdebug.trace_output_dir => /tmp => /tmp xdebug.trace_output_name => crc32 => crc32 Environment XDEBUG_CONFIG => remote_handler=gdb

derick 2005-03-10 22:42 administrator ~0000248	Is this still a problem with the latest CVS version of Xdebug?

emgie 2005-03-17 16:22 reporter ~0000250	Today I've tried the latest Xdebug version and I can reproduce the error, however only using php command line program. PHP module for apache seems to work well. Tried with PHP 5.0 and 4.3.3. I will be trying to reproduce this at home, on Mandrake Linux 9.1.

derick 2006-01-17 21:30 administrator ~0000340	I can still not reproduce this, so I'm marking this bug as "unable to duplicate". If you can provide more information, please reopen.

derick 2006-02-21 22:34 administrator ~0000371	I did see this error when running Xdebug with Komodo, so it seems to be valid. Will need to dig into this though.

emgie 2006-02-22 09:55 reporter ~0000373	I can confirm the bug's existence on the Fedora Core 4 with updates: PHP version 5.0.4, xdebug 2.0.0rc1-dev, Apache/2.0.54 (Fedora). The same code used to reproduce the bug.

derick 2006-03-09 14:06 administrator ~0000382	Fixed in CVS! (finally :) )