Exerb problem

Hi Nobu,

Thank you, that helped.

However, after extending the script somewhat I now get
"Segmentation faults" at various locations in the script.

Another question (excuse me I’m a newbie):

Why does it take longer time to read large files (in blocks
of 2**18 bytes) when in binary mode (opened with “rb”) as
compared to normal mode (opened with “r”)?

It takes about 5-10 times longer in binary mode. Is this
a known problem and is there a workaround? This is really
unrelated to exerb since it happens also when running the
script directly.

Thanks for taking your time,

Karsten

···


http://fastmail.fm - Email service worth paying for. Try it for free

coma_killen@fastmail.fm wrote:

Another question (excuse me I’m a newbie):

Why does it take longer time to read large files (in blocks
of 2**18 bytes) when in binary mode (opened with “rb”) as
compared to normal mode (opened with “r”)?

It takes about 5-10 times longer in binary mode. Is this
a known problem and is there a workaround? This is really
unrelated to exerb since it happens also when running the
script directly.

This is a known problem for the mswin32 build of Ruby 1.6.7 (which exerb
is based on). I’m sorry that I can’t point you to a particular ruby-talk
thread but maybe someone else knows the particulars. It is fixed for
Ruby 1.7.x (and possibly in the 1.6 CVS branch).

Hi,

However, after extending the script somewhat I now get
"Segmentation faults" at various locations in the script.

Hmmm, I don’t know about detail of exerb and PE format, so
reported to exerb developers ML.

Why does it take longer time to read large files (in blocks
of 2**18 bytes) when in binary mode (opened with “rb”) as
compared to normal mode (opened with “r”)?

It’s known problem, IO in 1.6 is slow and mswin32 version is
more, however, I don’t remember about open mode.

IO#sysread may help you.

···

At Thu, 19 Sep 2002 21:51:25 +0900, coma_killen@fastmail.fm wrote:


Nobu Nakada