Report - New

Package home | Report new bug | New search | Development Roadmap

Status: Open | Feedback | All | Closed Since Version 0.4.0

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 "bogus."
If you feel this bug concerns a security issue, eg a buffer overflow, weak encryption, etc, then email pear-group who will assess the situation.

Note:
Please supply any information that may be helpful in fixing the bug:

The version number of the PEAR 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 (not your whole php.ini!)
A gdb backtrace.

Your email address: MUST BE VALID
PHP version:
Package version:	How to retrieve that?
Package affected:	PHP_LexerGenerator
Bug Type:
Operating system:
Solve the problem : 47 + 27 = ?
Summary:
Description: Put code samples in the "Test script" section below and upload patches below.
	I have files to attach to this report
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 or attach a patch that will reproduce the bug.
Expected result: What do you expect to happen or see when you run the test script above?
Actual result: This could be a backtrace for example. Try to keep it as short as possible without leaving anything relevant out.