Announcement

Collapse
No announcement yet.

PBDLL -> DEBUG FILE is very slow

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

  • PBDLL -> DEBUG FILE is very slow

    Dear

    I recognize that PB is super quick, but when I execute PB DEBUG and I fix a BREAKPOINT it is the slowest thing that I have seen (8086 Zzzz)

    I need a solution

    Note: I use a PENTIUM II of 500MHZ..


    Regards

    Amauri

    ------------------

  • #2
    Hello,

    I personally don’t care for the debug program that comes with PB. It has many shortcomings that are on the customers ‘wish list’ for future releases. However, while we wait, most PB programmers (from what I read on this forum anyway) have switched to other debug methods. These have actually become more useful to me that a traditional debugger. A few suggestions are:

    The number one debug tool in PB is the MSGBOX statement. Not that it is unique to PB, but it is however an excellent way to find out what is going on. Be careful in loops however, and maybe add and check the return after using the %YESNO equate option to allow you to exit the loop by click on the No button.

    The second way is to use a log file. If you use the simple OUTPUT method and then PRINT# it is rather easy and quick. Another idea here is to use an equate or global variable to turn on and off the debug file printing throughout the entire program. IF %DEBUGPRINT = %TRUE THEN PRINT#

    There was a good long tread on this topic a short while ago, so maybe do a search in this forum on ‘debug’ and you’ll find a lot of ideas.

    Colin Schmidt

    ------------------
    Colin Schmidt & James Duffy, Praxis Enterprises, Canada
    [email protected]

    Comment


    • #3
      I parse pages of ASCII reports and populate a database, and to
      do my debugging I use this code. It works better than MSGBOX
      because I can actually see a whole window full of text if I want,
      and copy and past it etc etc... It works pretty good, although
      of Win9x you should change it to wordpad.exe if the buffer is
      very large.

      Hope that helps

      Code:
      SUB debug(sBuffer$)
          a& = FREEFILE: OPEN "C:\tmp.tmp" FOR BINARY AS a&
          SETEOF a&:PUT a&,,sBuffer$:CLOSE a&
          SHELL "C:\winnt\system32\notepad.exe c:\tmp.tmp"
      END SUB
      
      FUNCTION PBMAIN() AS LONG
          debug "test"
      END FUNCTION
      ------------------
      -Greg
      -Greg
      [email protected]
      MCP,MCSA,MCSE,MCSD

      Comment


      • #4
        thank you

        you helped me enough

        regards

        amauri

        ------------------

        Comment

        Working...
        X