[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

serialport bug on w2k - will it get fixed?

chris

10/24/2004 2:49:00 AM

using ruby 1.8.1 (the most recent 2
or so release candidates..i haven't tried more)
on w2k results in an error and crashes
when using SerialPort

someone else described the bug here:
http://rubyforge.org/tracker/index.php?func=detail&aid=560&group_id=61&am...

the error does NOT occur when running the same
code on the same machine with all other things equal
except the use of ruby 1.8.0 instead.

can/will this bug be fixed? is there somebody
who can take a look?

any thoughts?



3 Answers

chris

10/24/2004 2:56:00 AM

0

PS: i ask because:

1) this has been seemingly known and outstanding for a long time;
is the serialport code dead?

2) based on the "feel" of the bug (since everthing else seems to work
in all other situation on all other platforms) it would appear to be
more of catching a one-line mistake somewhere instead of writing
or re-writing lines of code (and also because it used to work on the
previous version) i'm hoping there can't be *that* many changes to
the source code in that area of ruby and I suspect that a 'guru' type
could find it maybe in minutes (?)

3) simply staying with ruby 1.8.0 for w2k people isn't much of a
solution and despite my attempts the bug appears assigned to nobody and
of concern to nobody. i don't see anything showing a fix is already
in 1.8.1 final or planned otherwise

(no. i don't have the skills to fix it myself unfortunately)


----- Original Message -----
From: "chris" <nospam@spammersgoaway.fu>
Newsgroups: comp.lang.ruby
Sent: Saturday, October 23, 2004 10:48 PM
Subject: serialport bug on w2k - will it get fixed?


> using ruby 1.8.1 (the most recent 2
> or so release candidates..i haven't tried more)
> on w2k results in an error and crashes
> when using SerialPort
>
> someone else described the bug here:
>
http://rubyforge.org/tracker/index.php?func=detail&aid=560&group_id=61&am...
>
> the error does NOT occur when running the same
> code on the same machine with all other things equal
> except the use of ruby 1.8.0 instead.
>
> can/will this bug be fixed? is there somebody
> who can take a look?
>
> any thoughts?
>
>
>


chris

10/24/2004 7:17:00 AM

0

correction: problem occurring with ruby 1.8.2 rc8a



> ----- Original Message -----
> From: "chris" <nospam@spammersgoaway.fu>
> Newsgroups: comp.lang.ruby
> Sent: Saturday, October 23, 2004 10:48 PM
> Subject: serialport bug on w2k - will it get fixed?
>
>
> > using ruby 1.8.1 (the most recent 2
> > or so release candidates..i haven't tried more)
> > on w2k results in an error and crashes
> > when using SerialPort
> >
> > someone else described the bug here:
> >
>
http://rubyforge.org/tracker/index.php?func=detail&aid=560&group_id=61&am...
> >
> > the error does NOT occur when running the same
> > code on the same machine with all other things equal
> > except the use of ruby 1.8.0 instead.
> >
> > can/will this bug be fixed? is there somebody
> > who can take a look?
> >
> > any thoughts?
> >
> >
> >
>
>



Markus

10/25/2004 2:20:00 PM

0

On Sat, 2004-10-23 at 19:59, chris wrote:
> PS: i ask because:
>
> 1) this has been seemingly known and outstanding for a long time;
> is the serialport code dead?
>
> 2) based on the "feel" of the bug (since everthing else seems to work
> in all other situation on all other platforms) it would appear to be
> more of catching a one-line mistake somewhere instead of writing
> or re-writing lines of code (and also because it used to work on the
> previous version) i'm hoping there can't be *that* many changes to
> the source code in that area of ruby and I suspect that a 'guru' type
> could find it maybe in minutes (?)
>
> 3) simply staying with ruby 1.8.0 for w2k people isn't much of a
> solution and despite my attempts the bug appears assigned to nobody and
> of concern to nobody. i don't see anything showing a fix is already
> in 1.8.1 final or planned otherwise
>
> (no. i don't have the skills to fix it myself unfortunately)
>

Nor do I. But together...who knows?

If this is important to you, I will try to help. If we block off
all the exits, we might be able to corner the bug and shine a bright
light on it. As it cowers there, exposed and helpless under our
scrutiny, perhaps someone who _can_ fix it will reach over with a rolled
up newspaper and *whack!* our troubles will be over. (We hope, of
course, that the sound will be that of them hitting the bug, not us.)

I do not have any MS windows machines, so I can't compile or test,
but I can look at the source code, and often even understand it. You
have a version of ruby that exhibits a problem, and another that does
not. Can you compile from source? If so, we can look for differences
between the source of the the version that works and the one that
doesn't. We can then test our assumptions by unmaking the change to see
if that fixes the problem. If we get that far I suspect we can induce
others to help us.

-- Markus




> > using ruby 1.8.1 (the most recent 2
> > or so release candidates..i haven't tried more)
> > on w2k results in an error and crashes
> > when using SerialPort
> >
> > someone else described the bug here:
> >
> http://rubyforge.org/tracker/index.php?func=detail&aid=560&group_id=61&am...
> >
> > the error does NOT occur when running the same
> > code on the same machine with all other things equal
> > except the use of ruby 1.8.0 instead.
> >
> > can/will this bug be fixed? is there somebody
> > who can take a look?
> >
> > any thoughts?
> >
> >
> >
>
>