[erlang-questions] Call for bugs

Shayan Pooya shayan@REDACTED
Fri Jun 13 16:02:42 CEST 2014


I occasionally see some errors that I am a little surprised that dialyzer
did not catch. For example these commits are fixing some issues that could
have been caught by type analysis but dialyzer did not catch them:

1. https://github.com/discoproject/disco/commit/78e388020
2. https://github.com/discoproject/disco/commit/57953a9d29420
3. https://github.com/discoproject/disco/commit/8550179b5efb44
4. https://github.com/discoproject/disco/commit/1b7bfc4161f37

On Fri, Jun 13, 2014 at 7:57 AM, Salvador Tamarit <
stamarit@REDACTED> wrote:

> Hi all,
> we are working in an alternative debugger for Erlang based on the concept
> of declarative debugging. We have found some difficulties finding
> interesting buggy programs to test our tool, so we think that maybe you all
> can help us in this. We will need examples of buggy functions or modules
> or, if it exits, a place where there is a collection of them. Also any bug
> that you remember that was difficult to solve in order to try to reproduce
> it again in a new program. We are more interested in bugs that Dialyzer
> can't find, because the intention of the tool is to help to find bugs after
> running Dialyzer.
> Thanks in advance for your collaboration.
> Salvador Tamarit
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140613/432e3c06/attachment.htm>

More information about the erlang-questions mailing list