General

Home

Bug Reporting

Reporting Bugs via Bugzilla

ECLiPSe Bugs Database

Reporting Bugs by Email

eclipse-clp-bugs@lists.sourceforge.net

• The ECLiPSe version number and configuration
• Machine type
• Operating system name and version number
• Your .eclipserc and ECLIPSE... environment variables, if used
• A script which causes the bug to appear, enhanced by comments where necessary (start from the ECLiPSe banner unless the option -e is used):

Bug Reporting Guidelines

If you want to report a problem, first make sure that it is really a bug in the system and not in your program or in your interpretation of the ECLiPSe functionality. If you are not sure whether you have found a bug, here are some guidelines:

• If you get a Unix Segmentation violation or Windows Exception, you may have found a bug in ECLiPSe. However, certain operations on cyclic or very deeply nested terms can cause machine stack overflows which show the same symptom, and are not considered a bug. The problem could also be caused by an error in an external C/C++ function, in case you use those. If none of these alternative explanations apply, you should report the problem.
• All 'internal' messages like

      Compiler internal error: ...
      GC internal error: ...
  

  and similar ones indicate an ECLiPSe bug.
• If you supply bad mode declarations, the behaviour of your program is undefined. This is not a bug.

We can fix your problem only if we are able to reproduce it. This means that it is absolutely necessary to include a script which shows, from the beginning of an ECLiPSe session, what is to be done to make the problem appear. Vague statements like "I have found a bug in the assert predicate" or "the setval/2 predicate crashes when I store a ground term more than 50 times" are of little use.

In general, you help us if you try to narrow down the problem. Especially if your program just fails or gives wrong solutions, it is very difficult for us to find where something goes wrong as we are not familiar with your program. On the other hand, if you get a Segmentation violation or 'internal error' message, we can usually find the problem without understanding your program, so you don't need to waste time with narrowing down.