In case you have problems with remote debugging, eliminate all references to WinTypes and WinProcs in your uses clauses. Don't forget the third party libraries you are using.

-
In case you have problems with remote debugging, eliminate all references to WinTypes and WinProcs in your uses clauses. Don't forget the third party libraries you are using.

The symptom is: no blue dots when running the app in the remote debugger.

Comments

  1. Asbjørn HeidMay 7, 2013 at 11:50 AM

    Yeah that makes sense... ?

    ReplyDelete
  2. Uwe RaabeMay 7, 2013 at 12:41 PM

    Asbjørn Heid Actually I don't know why it worked. Thought it was worth to share the tip.

    ReplyDelete
  3. Ilya SMay 7, 2013 at 12:42 PM

    Oh, common! What's the connection?

    ReplyDelete
  4. Asbjørn HeidMay 7, 2013 at 12:45 PM

    Uwe Raabe Yeah sounds random. Then again that seems to be a common theme with these newfangled Delphi releases :P

    ReplyDelete
  5. Uwe RaabeMay 7, 2013 at 1:44 PM

    WinTypes and WinProcs are no real units. They are both an alias for Winapi.Windows. The IDE and the compiler silently resolve the alias even without setting it in the compiler options. Perhaps the remote debugger is not that clever. At least those names make it into the rsm file.

    ReplyDelete
  6. Ilya SMay 7, 2013 at 9:51 PM

    Uwe Raabe btw, are you talking about new PAServer or old Remote debugger?

    ReplyDelete
  7. Uwe RaabeMay 8, 2013 at 12:24 AM

    Ilya S The problem occured in XE3 PAServer using QuickReport, but AFAIK PAServer calls the old remote debugger for Win32 apps. Actually QuickReport uses IFDEFs to use WinProcs, WinTypes only for Delphi 1 projects (huh? They mention D5+ on their website! Time to clean up guys!), but in qrexpr.pas one slipped through, leading to a uses clause containing WinProcs, WinTypes and Windows without complaints from the compiler.

    ReplyDelete

Post a Comment