search

catb0t / propforth

Automatically exported from code.google.com/p/propforth
0 stars 0 forks source link

20140102 errors #214

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

Using build from 20140102

frida reports more of the lockup after lockup after Startkernel.spin

http://forums.parallax.com/showthread.php/152568-PropForth-6-development?p=12332
68&viewfull=1#post1233268

using windows 7 rig with hardware:
Windows 7 ASUS Eee PC Intel Atom CPU D525@1.80GHz 1.80GHz RAM 2GB 32- bit 
operating system

http://forums.parallax.com/showthread.php/146693-Propforth-v5.5-is-available-for
-download?p=1226009&viewfull=1#post1226009

Original issue reported on code.google.com by prof.bra...@gmail.com on 7 Jan 2014 at 10:18

GoogleCodeExporter commented 8 years ago 
Can you please zip up the results directory any time you get a failure, as well 
please attach the files you are running if they are different.

This may help pinpoint where the failure is occurring, and suggest where some 
debugging code is necessary.

Original comment by salsa...@gmail.com on 7 Jan 2014 at 11:16

GoogleCodeExporter commented 8 years ago 
There are more details to poul investigation in the forum thread, particularly 
post 12, 
http://forums.parallax.com/showthread.php/152568-PropForth-6-development?p=12309
41&viewfull=1#post1230941

and posts 15 to 18
http://forums.parallax.com/showthread.php/152568-PropForth-6-development?p=12325
17&viewfull=1#post1232517

Original comment by prof.bra...@gmail.com on 8 Jan 2014 at 6:28

GoogleCodeExporter commented 8 years ago 
Looked at those,the reason I need the logs as well as a snapshot and the 
console output is to determine if the failure is happening as goterm finishes, 
or afterwards.

I have had no failures in goterm in 30+ builds now, so I am suspecting 
something else is going on, but I need some data.

If you can repro a failure, the data will help isolate the issue.

Original comment by salsa...@gmail.com on 8 Jan 2014 at 9:51

GoogleCodeExporter commented 8 years ago 
As for the buffer size, the driver on the PC should have ample buffering and 
should not overrun the ic's buffers. My testing however indicates there is some 
problem somewhere, and the buffers can be overrun. The symptom was a single 
dropped character one every 3 hours or so running at full speed.

With the changes to the buffer size and a delay, I have never seen this failure 
again. The change in the buffer size alone did not eliminate this issue.

Given the behavior I suspect there is a boundary issue in the driver.

Original comment by salsa...@gmail.com on 8 Jan 2014 at 9:58

GoogleCodeExporter commented 8 years ago

Original comment by prof.bra...@gmail.com on 10 Jan 2014 at 3:36