View on
Chris Marshall > PDL > PDL::Bugs


Annotate this POD


View/Report Bugs
Source   Latest Release: PDL-2.018_01


PDL::Bugs - How to diagnose and report PDL problems


version 1.0000


This module explains how to get help with a PDL problem and how, when, and where to submit a bug report. In the future it may be extended to provide some sort of automated bug reporting capability.


The primary resource for support for the Perl Data Language is via the PDL mailing lists. The pdl-general list is for general use and discussions and is the one to use for questions about problems with PDL or PDL use for computation. This is almost always the list to post to for PDL problems.

The pdl-devel list is specifically for PDL development and often contains discussions of a rather technical nature relating to PDL internals. This is not the list for general PDL discussion or questions.

NOTE: Both pdl-general and pdl-devel are read by the PDL developers so you don't save time or increase the probability of response by posting to pdl-devel or by cross-posting to pdl-devel. Please stick to pdl-general list posts unless you want to talk PDL implementation and development.

NOTE: There is also a PDL IRC channel which can be useful for immediate questions if populated. However, it has the big disadvantage of not being easily searched or routinely read by all PDL developers and users. As a result, if you get an answer there, it may be incorrect or incomplete depending on who happens to be chatting at the time. It is definitely not readily searchable.


Please submit bug reports via the sourceforge bug tracker interface at

where you can review the previously submitted bug reports. Click on Create Ticket to generate a bug report. If you do not already have a account, you will need to get one to submit the report:

Please provide a way for the PDL developers to contact you regarding the problem.

Try to include any information you think might help someone isolate, reproduce, and fix your problem.

At a minimum, include the following information:

Other things that are often helpful:

Alternatively, send an e-mail report with the above information (including the output of perldl -V) to See

for info on how to subscribe to this list.


BEFORE you report a bug make sure you got the latest release version of PDL, always available from CPAN, check

Also, you can check the FAQ at

and the mailing list archives for hints. You can find links to the searchable archives at

and there is a Google enable search box on the top right of which usually gives the best results.


Patches can be sent to the pdl-devel mailing list (see above) or can be directly submitted to the patch manager

Patches should be made against the latest released PDL or, ideally, against the current git sources which you can browse and check out at


Thanks, The PDL developers.

syntax highlighting: