Announcement

Collapse
No announcement yet.

Unwanted behaviour in PBDLL IDE

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

  • Unwanted behaviour in PBDLL IDE

    using PB/DLL 6.0 IDE to Debug code,
    If Set Primary Module is used
    AND
    a module with diffrent path than primary module is topmost window
    while compile/debug
    compilation will end ok but debugger will not find debugger
    symbole file PBDLLTMP.PBD


    -------------
    Fred
    mailto:[email protected][email protected]</A>
    http://www.oxenby.se



    [This message has been edited by Fred Oxenby (edited April 26, 2000).]
    Fred
    mailto:[email protected][email protected]</A>
    http://www.oxenby.se

  • #2
    Thanks! I'll pass this along to R&D. Essentially, the IDE expects the files to be located in the current (working) directory - if you load a file and change directories to load the file, the "current" directory changes. Code that expects to find datafile in the current directory should explicitly set the directory at runtime (at least during development).

    There is another issue along the same lines too, if my memory serves me well... if a #INCLUDE metastatement contains a non-complete (relative) path, and there is an compile-time error in this file, the IDE is not able to locate the file and issues an error in the form of a MSGBOX. I've already sent this report to R&D.

    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>
    Lance
    mailto:[email protected]

    Comment


    • #3
      Lance, I never use 'complete paths' in my #Include metacommand.
      All includes are referenced from the path of the Project.
      Example:
      Code:
      #Compile Exe "..\CVT_DLL\TEST.EXE"
      #include "..\COMMON\FILE1.BAS"
      #include "..\RUNTIME\FILE2.BAS"
      etc..
      This setup is perfect as long as I do not need to debug part
      of my code.
      If I must debug, I have to create a small Test-stub in the "..\CVT_DLL\" path above
      (where all DLL-s and Exes are located)
      and start the IDE-session from this file.
      This works smooth for me.
      I would very much like the compiler to look at the #compile metacommand
      to determine where to put PBDLLTMP.EXE and PBDLLTMP.PBD when
      compile/debug is invoked,
      as it does when compile/run is invoked.
      I think it is what we in Sweden call "in-consequent" behavior
      Do you think we will get a stand-alone (from IDE) debugger soon?



      ------------------
      Fred
      mailto:[email protected][email protected]</A>
      http://www.oxenby.se

      Fred
      mailto:[email protected][email protected]</A>
      http://www.oxenby.se

      Comment


      • #4
        I'm not aware of any plans to do so, but you should send the idea to mailto:[email protected][email protected]</A> so that the idea gets onto the wish-list.


        ------------------
        Lance
        PowerBASIC Support
        mailto:[email protected][email protected]</A>
        Lance
        mailto:[email protected]

        Comment

        Working...
        X