php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

Before you report a bug, make sure to search for similar bugs using the "Bug List" link. Also, read the instructions for how to report a bug that someone will want to help fix.

If you aren't sure that what you're about to report is a bug, you should ask for help using one of the means for support listed here.

Failure to follow these instructions may result in your bug simply being marked as "not a bug."

Report PEAR related bugs here

If you feel this bug concerns a security issue, e.g. a buffer overflow, weak encryption, etc, then email security@php.net who will assess the situation or use Security as bug type in the form below.

Your email address:
MUST BE VALID
Password:
You must enter any password here, which will be stored for this bug report.
This password allows you to come back and modify your submitted bug report at a later date. [Lost a bug password?]
PHP version:
Package affected:
Bug Type:
Operating system:
Summary:
Note: Please supply any information that may be helpful in fixing the bug:
  • The version number of the PHP package or files you are using.
  • A short script that reproduces the problem.
  • The list of modules you compiled PHP with (your configure line).
  • Any other information unique or specific to your setup.
  • Any changes made in your php.ini compared to php.ini-dist or php.ini-recommended (not your whole php.ini!)
  • A gdb backtrace.
Description:

Put short code samples in the "Test script" section below and upload patches and/or long code samples below.

Test script:

A short test script you wrote that demonstrates the bug. Please do not post more than 20 lines of code. If the code is longer than 20 lines, provide a URL to the source code that will reproduce the bug.

Patch name

The patch name must be shorter than 80 characters and it must only contain alpha-numeric characters, dots, underscores or hyphens.


Patch file:

A patch file created using git diff (unified diff format)

Expected result:

What do you expect to happen or see when you run the test script above? Leave it empty if irrelevant (e.g. you're going to duplicate description here).

Actual result:

This could be a backtrace for example. Try to keep it as short as possible without leaving anything relevant out. Leave it empty if irrelevant (e.g. you're going to duplicate description here).

Solve the problem:
30 + 36 = ?
Submit:
 
PHP Copyright © 2001-2014 The PHP Group
All rights reserved.
Last updated: Sat Apr 19 12:01:52 2014 UTC