[erlang-bugs] erl_interface: badarg on specific inputs

[Davide Marquês]

Hi all,

I hope I'm not abusing this mailing list with this email. I posted the
problem
earlier today on erlang-questions:
http://www.erlang.org/pipermail/erlang-questions/2009-May/043577.html
but I'm guessing there aren't many erl_interface [on windows] users.
Since this might be a bug here goes...

Under certain inputs my basic port programs are simply breaking:

4> echo:echo("aaa aaaaaa").
sending to port: {echo,{"aaa aaaaaa"}}

=ERROR REPORT==== 4-May-2009::16:11:15 ===
catch: error:badarg

This might be simply due to bad coding on my part but I've tried to keep it
simple to rule that out. I was able to replicate the problem with
erl_interface-3.6.1
(.lib that come with the binary windows distribution; a MSVC build; and a
MinGW build)
and erl_interface-3.5.9 (MinGW build only).

The [failing] code is available here:
http://github.com/davide/erl_interface-examples/tree/master
A sure way to get the echo program to fail is: echo:echo("New Folder").

I'm welcoming any feedback! Even if it's just to point out that I'm doing
something
really dumb (I can live with that). :)

On a side note, on the docs folder I documented my experience of trying
(and failing) to build erlang on Windows (using Visual C++ 2008 Express
Edition).
As the details might be revelant to other users please consider updating
README.WIN32 to get it into a step-by-step/How-To
style<http://github.com/davide/erl_interface-examples/blob/1443a11bd6aa5aa4b6030c9fec1d6c4ff360dd57/doc/Building%20erlang%20on%20Windows.txt>
.

Cheers,
:Davide
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20090505/6e5c7a4a/attachment.htm>