Ergebnis der Suchanfrage

• Forum: Die Delphi-IDE

  AW: DLL debuggen

   
    by Kas Ob., 15. Nov 2023
  One more thing,
  After confirming if that does have something to do files and parsing, we (i mean you) will have to use ProcMon or the great ApiMonitor to compare how the IDE and its debugger behave and fail if there is a failure on some IO access, or did they read the whole TDS info or stopped parsing the header.
• Forum: Die Delphi-IDE

  AW: DLL debuggen

   
    by Kas Ob., 15. Nov 2023
  OK, while i didn't completely understand the first two lines in post #35, but let me explain again, and sorry for the bad English.
  
  We need to approach this by logic, so we can form a theory then test it, confirm a reason only after that will fix it for good, not leaving it to hit and miss and probable will work, you have testing bed with all these many files so it will be great for testing,...
• Forum: Die Delphi-IDE

  AW: DLL debuggen

   
    by Kas Ob., 14. Nov 2023
  There is also something to try, move both the EXE and DLL into one folder and make sure the IDE doesn't have any opened projects, then debug from there or attach to running process.
• Forum: Die Delphi-IDE

  AW: DLL debuggen

   
    by Kas Ob., 14. Nov 2023
  I am not sure that understand half of the former posts due the translation.
  
  And sorry if that i am missing the point.
  This line brings me to something i saw in either D2009 and D2010 years back, (or it was D2010 and XE5, i really can't remember)
  Process start: C:\Develop\ActiveScripting\ Win32 \Debug\Scripting.e xe. Base address: $00EC0000. Process Scripting.exe (8064)
  Load module:...