From: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
To: Stas Miasnikou <stas.miasnikou@gmail.com>
Cc: Martin Jambon <martin.jambon@ens-lyon.org>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Buffer.add_channel hangs
Date: Thu, 18 Mar 2010 10:09:47 +0100 [thread overview]
Message-ID: <4BA1EDDB.8030702@inria.fr> (raw)
In-Reply-To: <36ae71be1003172347x469625a5o8de8c5637d5727ff@mail.gmail.com>
Hi,
Maybe you should just use (in_channel_length ic) to get the size of the
file before hand, so that you can directly create a string with that
size instead of a Buffer.t ?
Regards,
--Fabrice
Stas Miasnikou wrote, On 03/18/2010 07:47 AM:
> On 3/18/10, Martin Jambon <martin.jambon@ens-lyon.org> wrote:
>> Stas Miasnikou wrote:
>>> OCaml 3.11.1, OpenBSD 4.6, i386.
>>>
>>> I am trying to read whole file by doing:
>>>
>>> let read_file_bin name =
>>> let ic = open_in_bin name in
>>> let b = Buffer.create 1024 in
>>> (try Buffer.add_channel b ic max_int with _ -> ()); (* <-- HERE *)
>>> close_in ic;
>>> Array.init (Buffer.length b) (fun i -> int_of_char (Buffer.nth b i))
>>>
>>> but it hangs on the line marked. Am I doing something wrong?
>> The problem is max_int and the fact that Buffer.add_channel and
>> Buffer.resize
>> do not check for this possibility:
>>
>> let add_channel b ic len =
>> if b.position + len > b.length then resize b len;
>> really_input ic b.buffer b.position len;
>> b.position <- b.position + len
>>
>> Something like the following would be better:
>>
>> let add_channel b ic len =
>> if len < 0 || len > Sys.max_string_length then
>> invalid_arg "Buffer.add_channel";
>> ...
>
> Oh, never thought OCaml has bugs! ;-)
>
>> Since you uncovered this problem, please kindly submit a proper bug report
>> at
>> http://caml.inria.fr/mantis
>
> I've submitted it.
>
>> (and figure what to do if the file is larger than 16MB on 32-bit systems)
>>
>> Of course, you can see from the implementation of the Buffer module that a
>> string of your maximum length is created no matter what, which you surely
>> want
>> to avoid especially on 64-bit systems where Sys.max_string_length is very
>> large.
>
> Erm... yes. I think I follow the other advice and will use Bigarray.
>
> Stas
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
--
Fabrice LE FESSANT
Chercheur, Equipe ASAP
(As Scalable As Possible)
http://www.lefessant.net/
INRIA-Futurs, Bat P - 112
Parc Orsay Université
2-4, rue Jacques Monod
F-91893 Orsay Cedex, FRANCE
next prev parent reply other threads:[~2010-03-18 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 20:27 Stas Miasnikou
2010-03-17 23:20 ` [Caml-list] " Martin Jambon
2010-03-18 6:47 ` Stas Miasnikou
2010-03-18 9:09 ` Fabrice Le Fessant [this message]
2010-03-18 2:53 ` Goswin von Brederlow
2010-03-18 17:52 ` Stas Miasnikou
2010-03-20 8:29 ` Stas Miasnikou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA1EDDB.8030702@inria.fr \
--to=fabrice.le_fessant@inria.fr \
--cc=caml-list@yquem.inria.fr \
--cc=martin.jambon@ens-lyon.org \
--cc=stas.miasnikou@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox