Shop OBEX P1 Docs P2 Docs Learn Events
Compiler bug? chip damaged? (Never mind) — Parallax Forums

Compiler bug? chip damaged? (Never mind)

Erik FriesenErik Friesen Posts: 1,071
edited 2009-12-25 17:52 in Propeller 1
Here is an oddity. Help me with what I am missing.

In my debugging here, commenting out the line following the return makes a difference.



Pri Settings | choose,pword,resettime,ckpos,prpos,repos
return
text.out(0)
                                          
repeat until btn==1 and selector==0




here is the calling line

if position==2
      repeat until btn==1 and selector==0
      settings
      text.out($0)
      repeat until btn==1 and selector==0
      position:=2
      menudisplay



Must have been some left over code calling my i2c object.

Post Edited (Erik Friesen) : 12/25/2009 7:18:21 PM GMT

Comments

  • mparkmpark Posts: 1,305
    edited 2009-12-25 17:49
    I'll bite. What difference does it make?
  • Erik FriesenErik Friesen Posts: 1,071
    edited 2009-12-25 17:52
    It stops my top thread. Here is where a debugger would be so handy. I think it has something to do with my stack space somewhere. I have 935 free, but when I comment miscellaneous areas or code out, my program alternates between running and not.

    What is the minimum free required?
Sign In or Register to comment.