1. Rob: Bug in PD Eu v2.5 found
- Posted by Al Getz <Xaxo at aol.com>
Nov 18, 2005
-
Last edited Nov 19, 2005
Hello there,
I ran into a bug while testing a program under PDEU 2.5 today.
The bug occurs while in the trace screen, and the main issue is
that trace lines get repeated. For example (within a function):
214: x=1
214==> x=1
would be a typical trace screen display just before hitting enter
to actually get x to be equal to 1. The problem continues as you
hit enter, with lines being 'doubled' like that until the function
exits.
The problem occurs within a function body just AFTER a line that is
very long (238 characters made up of a huge calculation involving
additions, subtractions, and multiplications and one divide)
something like this:
y=(2*xx+yy+9*w-x*2*yy.......)/(c+d) --238 characters long
where "......." is adds, subtracts, and multiplies, similar to the
beginning of that statement.
Also, the line is within a function statement, and as noted the
'line doubling' goes away after the function returns, but remains up
until the actual return to the calling line.
Since it seems to occur only after the very long line (which v2.4 wont
accept) it looks like that's the only time it happens.
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
2. Re: Rob: Bug in PD Eu v2.5 found
- Posted by Robert Craig <rds at RapidEuphoria.com>
Nov 18, 2005
-
Last edited Nov 19, 2005
Al Getz wrote:
> I ran into a bug while testing a program under PDEU 2.5 today.
> The bug occurs while in the trace screen, and the main issue is
> that trace lines get repeated. For example (within a function):
>
> 214: x=1
> 214==> x=1
>
> would be a typical trace screen display just before hitting enter
> to actually get x to be equal to 1. The problem continues as you
> hit enter, with lines being 'doubled' like that until the function
> exits.
>
> The problem occurs within a function body just AFTER a line that is
> very long (238 characters made up of a huge calculation involving
> additions, subtractions, and multiplications and one divide)
> something like this:
> y=(2*xx+yy+9*w-x*2*yy.......)/(c+d) --238 characters long
> where "......." is adds, subtracts, and multiplies, similar to the
> beginning of that statement.
> Also, the line is within a function statement, and as noted the
> 'line doubling' goes away after the function returns, but remains up
> until the actual return to the calling line.
>
> Since it seems to occur only after the very long line (which v2.4 wont
> accept) it looks like that's the only time it happens.
There was a somewhat similar "long-line" trace bug in 2.5 alpha.
It was fixed several months ago. I hope you aren't still using 2.5 alpha
or beta. The old 2.4 trace expected lines to be fairly short, but in
2.5 the front-end no longer enforces any limit, so this caused a problem
which was fixed, I think in the beta, but definitely in the official
release.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
3. Re: Rob: Bug in PD Eu v2.5 found
- Posted by Matt Lewis <matthewwalkerlewis at gmail.com>
Nov 18, 2005
-
Last edited Nov 19, 2005
Robert Craig wrote:
>
> Al Getz wrote:
> > I ran into a bug while testing a program under PDEU 2.5 today.
> > The bug occurs while in the trace screen, and the main issue is
> > that trace lines get repeated.
<snip>
> There was a somewhat similar "long-line" trace bug in 2.5 alpha.
> It was fixed several months ago. I hope you aren't still using 2.5 alpha
> or beta. The old 2.4 trace expected lines to be fairly short, but in
> 2.5 the front-end no longer enforces any limit, so this caused a problem
> which was fixed, I think in the beta, but definitely in the official
> release.
I can confirm this bug (2.5 official). Try this code:
with trace
function foo()
integer x
x = 1 + 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1
x = 1
x = 2
x = 3
x = 4
return 1
end function
trace(1)
?foo()
Matt Lewis
4. Re: Rob: Bug in PD Eu v2.5 found
- Posted by Al Getz <Xaxo at aol.com>
Nov 18, 2005
-
Last edited Nov 19, 2005
Robert Craig wrote:
>
> Al Getz wrote:
> > I ran into a bug while testing a program under PDEU 2.5 today.
> > The bug occurs while in the trace screen, and the main issue is
> > that trace lines get repeated. For example (within a function):
> >
> > 214: x=1
> > 214==> x=1
> >
> > would be a typical trace screen display just before hitting enter
> > to actually get x to be equal to 1. The problem continues as you
> > hit enter, with lines being 'doubled' like that until the function
> > exits.
> >
> > The problem occurs within a function body just AFTER a line that is
> > very long (238 characters made up of a huge calculation involving
> > additions, subtractions, and multiplications and one divide)
> > something like this:
> > y=(2*xx+yy+9*w-x*2*yy.......)/(c+d) --238 characters long
> > where "......." is adds, subtracts, and multiplies, similar to the
> > beginning of that statement.
> > Also, the line is within a function statement, and as noted the
> > 'line doubling' goes away after the function returns, but remains up
> > until the actual return to the calling line.
> >
> > Since it seems to occur only after the very long line (which v2.4 wont
> > accept) it looks like that's the only time it happens.
>
> There was a somewhat similar "long-line" trace bug in 2.5 alpha.
> It was fixed several months ago. I hope you aren't still using 2.5 alpha
> or beta. The old 2.4 trace expected lines to be fairly short, but in
> 2.5 the front-end no longer enforces any limit, so this caused a problem
> which was fixed, I think in the beta, but definitely in the official
> release.
>
> Regards,
> Rob Craig
> Rapid Deployment Software
> <a href="http://www.RapidEuphoria.com">http://www.RapidEuphoria.com</a>
Hi again Rob,
I checked to make sure i was using the official release and not the beta.
Here's what i did:
Opened the program using the context menu and "Exw25.exe" ....problem
Opened the program using Exw25b.exw (the beta) ...problem
Copy and pasted the program into Exw25.exe (not the beta) ...still problem
When i downloaded the official release i made sure the beta was named
Exw25b and the new one Exw25 (without the 'b').
I also checked the entire registry for all Exw25.exe entries, and
all of them pointed to the correct directory and program name ie
"Euphoria25\bin\Exw25.exe" and NOT "Euphoria25b\bin\Exw25b.exe".
On opening the program the notes are:
Euphoria Interpreter 2.5 for 32-bit Windows.
Copyright (c) Rapid Deployment Software 2005
while the beta version says 'beta' in it too.
The download date (or release date?) is 03/07/2005
while for the beta is 01/13/2005,
but both programs have the same number of bytes.
Is this a bug or was there another release since 03/07 ?
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
5. Re: Rob: Bug in PD Eu v2.5 found
- Posted by Al Getz <Xaxo at aol.com>
Nov 18, 2005
-
Last edited Nov 19, 2005
Matt Lewis wrote:
>
> Robert Craig wrote:
> >
> > Al Getz wrote:
> > > I ran into a bug while testing a program under PDEU 2.5 today.
> > > The bug occurs while in the trace screen, and the main issue is
> > > that trace lines get repeated.
>
> <snip>
>
> > There was a somewhat similar "long-line" trace bug in 2.5 alpha.
> > It was fixed several months ago. I hope you aren't still using 2.5 alpha
> > or beta. The old 2.4 trace expected lines to be fairly short, but in
> > 2.5 the front-end no longer enforces any limit, so this caused a problem
> > which was fixed, I think in the beta, but definitely in the official
> > release.
>
> I can confirm this bug (2.5 official). Try this code:
> }}}
<eucode>
> with trace
> function foo()
> integer x
> x = 1 + 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
> 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
> 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
> 1+ 1+ 1+ 1+ 1
> x = 1
> x = 2
> x = 3
> x = 4
> return 1
> end function
>
> trace(1)
> ?foo()
> </eucode>
{{{
>
> Matt Lewis
Hey thanks Matt, i just confirmed i was using the official release
rather than the beta too. I named my .exe's different to avoid
that possible problem, but checked anyway.
Take care,
Al
And, good luck with your Euphoria programming!
My bumper sticker: "I brake for LED's"
6. Re: Rob: Bug in PD Eu v2.5 found
- Posted by Vincent <darkvincentdude at yahoo.com>
Nov 18, 2005
-
Last edited Nov 19, 2005
Al Getz wrote:
>
> Matt Lewis wrote:
> >
> > Robert Craig wrote:
> > >
> > > Al Getz wrote:
> > > > I ran into a bug while testing a program under PDEU 2.5 today.
> > > > The bug occurs while in the trace screen, and the main issue is
> > > > that trace lines get repeated.
> >
> > <snip>
> >
> > > There was a somewhat similar "long-line" trace bug in 2.5 alpha.
> > > It was fixed several months ago. I hope you aren't still using 2.5 alpha
> > > or beta. The old 2.4 trace expected lines to be fairly short, but in
> > > 2.5 the front-end no longer enforces any limit, so this caused a problem
> > > which was fixed, I think in the beta, but definitely in the official
> > > release.
> >
> > I can confirm this bug (2.5 official). Try this code:
> > }}}
<eucode>
> > with trace
> > function foo()
> > integer x
> > x = 1 + 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
> > 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
> 1+
> > 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
> > 1+ 1+ 1+ 1+ 1+ 1
> > x = 1
> > x = 2
> > x = 3
> > x = 4
> > return 1
> > end function
> >
> > trace(1)
> > ?foo()
> > </eucode>
{{{
> >
> > Matt Lewis
>
> Hey thanks Matt, i just confirmed i was using the official release
> rather than the beta too. I named my .exe's different to avoid
> that possible problem, but checked anyway.
>
>
> Take care,
> Al
>
> And, good luck with your Euphoria programming!
>
> My bumper sticker: "I brake for LED's"
It looks like the trace screen isn't refreshing properly when individual source
lines greatly exceed the viewable area.
http://img509.imageshack.us/img509/7563/trace3du.jpg
Regards,
Vincent
7. Re: Rob: Bug in PD Eu v2.5 found
Al Getz wrote:
>
> Matt Lewis wrote:
> >
> > Robert Craig wrote:
> > >
> > > Al Getz wrote:
> > > > I ran into a bug while testing a program under PDEU 2.5 today.
> > > > The bug occurs while in the trace screen, and the main issue is
> > > > that trace lines get repeated.
> >
> > <snip>
> >
> > > There was a somewhat similar "long-line" trace bug in 2.5 alpha.
> > > It was fixed several months ago. I hope you aren't still using 2.5 alpha
> > > or beta. The old 2.4 trace expected lines to be fairly short, but in
> > > 2.5 the front-end no longer enforces any limit, so this caused a problem
> > > which was fixed, I think in the beta, but definitely in the official
> > > release.
> >
> > I can confirm this bug (2.5 official). Try this code:
> > }}}
<eucode>
> > with trace
> > function foo()
> > integer x
> > x = 1 + 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
> > 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
> 1+
> > 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+ 1+
> > 1+ 1+ 1+ 1+ 1+ 1
> > x = 1
> > x = 2
> > x = 3
> > x = 4
> > return 1
> > end function
> >
> > trace(1)
> > ?foo()
> > </eucode>
{{{
> >
> > Matt Lewis
>
> Hey thanks Matt, i just confirmed i was using the official release
> rather than the beta too. I named my .exe's different to avoid
> that possible problem, but checked anyway.
Thanks Al and Matt.
I've confirmed it on my machine too.
I'll fix it for the next major release.
Regards,
Rob Craig
Rapid Deployment Software
http://www.RapidEuphoria.com
