Announcement

Collapse
No announcement yet.

PBWin 10.04 Crash During Debug

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • PBWin 10.04 Crash During Debug

    Not sure why, but my compiler has started to crash when starting a debug session. It does not appear to be associated with any particular code as it does it with everything!

    If I create a short simple program, set a break point and start a debug session, the program compiles and shows the first line high lighted ready to go, the variable watch window displays and all looks good, but …. When I double click the Variable Watch window, the Variable Evaluator displays correctly, type a variable name in the Name box, tick the ‘Watch’ checkbox and click OK, 9 times out of 10 the compiler crashes and everything closes.

    This is extremely irritating. I have tried reinstalling the compiler over the top of the original installation, but that has made no difference, the problem could be related to some corrupt data being left behind, but short of wiping everything, I can’t see how to resolve this issue, any one else had or seen anything similar?
    Richard

  • #2
    First guess. Nothing to do with PBWIn. We've seen similar occurences in the past.

    1. Check you anti-virus program logs.
    2. Try excluding the source code directory. from checking by your anti-virus program

    Comment


    • #3
      I had that problem also after an up date from MS. I had to change the permissions to administrator.
      Walt Decker

      Comment


      • #4
        Hi Stuart, excluding AV from source code makes no difference?
        Walt, allways logged on as Administrator, so looking more like a clean and install
        Richard

        Comment


        • #5
          What does program do when running NOT in debug mode?

          There are 'some' problems (code not shown) which can cause a failure the debugger cannot pick up; running outside the debugger will tell you if you have one of these issues.

          Right off the top of my head, this sounds like the same type of failure you get when you have inadequate stack.. as soon as program calls a procedure the program fails with little to no explanation.

          Michael Mattias
          Tal Systems (retired)
          Port Washington WI USA
          [email protected]
          http://www.talsystems.com

          Comment


          • #6
            Hi Michael,
            A code example can be something as simple as a FOR/NEXT loop with no code inside, the problem can show itself without even stepping into the code, just adding a watched variable can make the compiler fall over?
            Richard

            Comment


            • #7
              Richard. my guess is a generic memory corruption, caused by your code. Are you using all of these at the top of your source code?...

              #DIM ALL
              #DEBUG ERROR ON
              #DEBUG DISPLAY OFF


              ?

              "Not my circus, not my monkeys."

              Comment


              • #8
                Originally posted by richard robinson1 View Post
                , but …. When I double click the Variable Watch window, the Variable Evaluator displays correctly, type a variable name in the Name box, tick the ‘Watch’ checkbox and click OK, 9 times out of 10 the compiler crashes and everything closes.
                Changes in the Variable Evaluator probably result in an update of the PBWin.ini file.

                Check that the file isn't corrupted (or has become set to read only somehow?).
                You can delete this file and the IDE will recreate it automatically.

                Also check that your AV has the PBWin folders marked as excluded from real time scanning?
                Rgds, Dave

                Comment


                • #9
                  Originally posted by Dave Biggs View Post
                  Also check that your AV has the PBWin folders marked as excluded from real time scanning?
                  And that the PBWIN folders are not in a protected area such as "..\Program Files (x86)\..."


                  Comment


                  • #10
                    Hi Dave,
                    Changes in the Variable Evaluator probably result in an update of the PBWin.ini file.

                    Check that the file isn't corrupted (or has become set to read only somehow?).
                    You can delete this file and the IDE will recreate it automatically..
                    Sorry to say that did not work either.

                    Stuart, PBWin folders are excluded from my AV, but still PB crashes?

                    Richard

                    Comment


                    • #11
                      Originally posted by richard robinson1 View Post
                      Hi Dave,


                      Sorry to say that did not work either.

                      Stuart, PBWin folders are excluded from my AV, but still PB crashes?
                      What's the path to them?

                      Comment


                      • #12
                        What OS, which version of PBWin?
                        Can you post compilable code so others can test?
                        Rod
                        In some future era, dark matter and dark energy will only be found in Astronomy's Dark Ages.

                        Comment


                        • #13
                          Originally posted by Rodney Hicks View Post
                          ... which version of PBWin?
                          ...
                          I'd guess it's10.04 based on the thread Subject heading

                          Comment


                          • #14
                            Yeah, missed that didn't I! But there is still a void of information.
                            Rod
                            In some future era, dark matter and dark energy will only be found in Astronomy's Dark Ages.

                            Comment


                            • #15
                              Hi Guys,
                              Requested information is:-

                              PC Running Windows 10 Pro Version 1909
                              PBWin Version 10.04.0108

                              Example code:-
                              Code:
                              #COMPILER PBWIN 10
                              #COMPILE EXE "Test"
                              #OPTION VERSION5
                              #TOOLS OFF
                              #DEBUG ERROR ON
                              #DEBUG DISPLAY OFF
                              
                              
                              FUNCTION PBMAIN () AS LONG
                              LOCAL i AS LONG
                              
                              FOR i=1 TO 10
                                'Do nothing
                              NEXT
                              
                              END FUNCTION
                              But it ANY code will cause PB to fall over, so not a code issue.

                              In the example, try adding variable 'i' to watch list, will sometimes work, but most of the time PB will crash

                              Richard

                              Comment


                              • #16
                                Does the same thing happen on another PC? If NO then it's a PC problem.
                                <b>George W. Bleck</b>
                                <img src='http://www.blecktech.com/myemail.gif'>

                                Comment


                                • #17
                                  Your code does what it is supposed to do on my Win 10 PBWIN10 system.
                                  Rod
                                  In some future era, dark matter and dark energy will only be found in Astronomy's Dark Ages.

                                  Comment


                                  • #18
                                    Very weird. I tried it and it doesn't crash. So then set a watch on the i variable.

                                    In debug mode stepping through it the variable watch window shows i = 10, 9, 8, 7, ....

                                    Add a msgbox "I=" + format$(i)instead of the comment and i counts from 1 to 10 properly.

                                    ????????

                                    Comment


                                    • #19
                                      George, if the loop variable isn't addressed inside the loop, it will count backwards. At one time it always counted down but that caused some issues. Apparently it is more efficient to count down than up. IIRC
                                      Rod
                                      In some future era, dark matter and dark energy will only be found in Astronomy's Dark Ages.

                                      Comment


                                      • #20
                                        George,
                                        Does the same thing happen on another PC? If NO then it's a PC problem.
                                        Not sure, I don't have another PC with PB installed on it at the moment, but can give it a go.
                                        I susspect that it is more likely to be a file/DLL corruption somewhere, but i would have hoped that the reinstall would have fixed it, unless PB is using other system DLL's (which may) have been corrupted?
                                        Richard

                                        Comment

                                        Working...
                                        X