I've now got help from Embarcadero Support, and it turns out ot be a bug in rmtdbgXXX.exe which doesn't convert extended characters properly. So if you are logged on to the machine running RAD Studio with a username which contains some extended characters, then this will create a subdirectory to the scratch-dir with a directory name consisting of the username plus project name. This is where conversion fails so that the debugger can't find the symbol file. This has been logged as RS-63795.

But there is a workaround:
1) in the IDE go to Tools | Options | "Environment Options" | "Environment variables" | "System variables"
2) select USERNAME and Add Override
3) change the IDE's "local" username to a string without any extended chars
4) and the IDE will then pass THAT name over to PAServer and it will not cause rmtdbg the problem, and you do not need to create a new user on the machine.
Read More...

I now have
- "Link with dynamic RTL" = false
- "Link with Delphi Runtime library" = false
- "Link with runtime packages" = false

But when I open Deployment, I still see cc32150mt.dll, cc32150.dll, borlndmm.dll as DependencyModule, which sort of indicates that there is a dependancy to these DLL's. Or is that assumption incorrect?
Read More...

Hi,

Does anyone have an explanation to this? If I set Project/Options/Packages/Runtime Packages/Link with runtime packages to true, open Project/Deployment and click on Reconsile, then I see a lot more required libraries than if I set the option to false.

Shouldn't I see less required libraries if "Link with runtime libraries" is true?

Also, even if I set "Link with runtime libraries" to false, and "C++ Linker"/"Link with dynamic RTL" and "Link with Delphi runtime library" to true, Project/Deployment shows borlndmm.dll, cc32150.dll and cc32150mt.dll as required.
Is there any way to get all dependant DLL's included in the .exe ?
Read More...

I've now tested with a clean install of RAD Studio XE7 on Win7 x64 development host, and XE7 PAserver on target using the projects above. Still the same result: "No Debug Info"
Read More...

Hi,

Thanks for looking at this

Host: Win7 Ultimate x64 runing RAD Studio XE6 upd1
Targ: Win7 Ultimate x32 clean install, just rebooted

PAserver started

C++ console app with breakpoint
"Debug configuration - 32 bit Windows platform"
Target "32 bit Windows - Snotra-x32"
Press F9

Thread Start: Thread ID: 1048. Process Test2.exe (968)
Process Start: C:\Data\Embarcadero\PAserver\Administratör-Snotra-x32\Test2\Test2.exe. Base Address: $00400000. Process Test2.exe (968)
Module Load: Test2.exe. No Debug Info. Base Address: $00400000. Process Test2.exe (968)
Module Load: ntdll.dll. No Debug Info. Base Address: $76F60000. Process Test2.exe (968)
Module Load: KERNEL32.dll. No Debug Info. Base Address: $76040000. Process Test2.exe (968)

---

Restart IDE

C++ console app with breakpoint
"Debug configuration - 32 bit Windows platform"
Target "32 bit Windows - Snotra-x32", Project/Deployment, Click Connect Remote Machine, Remote Status "Same"
Press F9

Thread Start: Thread ID: 3416. Process Test2.exe (3380)
Process Start: C:\Data\Embarcadero\PAserver\Administratör-Snotra-x32\Test2\Test2.exe. Base Address: $00400000. Process Test2.exe (3380)
Module Load: Test2.exe. No Debug Info. Base Address: $00400000. Process Test2.exe (3380)
Module Load: ntdll.dll. No Debug Info. Base Address: $76F60000. Process Test2.exe (3380)
Module Load: KERNEL32.dll. No Debug Info. Base Address: $76040000. Process Test2.exe (3380)

---

Restart IDE

C++ console app with breakpoint
"Debug configuration - 32 bit Windows platform"
Target "32 bit Windows - Snotra-x32"
Run | Load Process | Remote Remote path: Test2\Test2.exe
Remote host: Snotra-x32
After load: Do not run
Load

Thread Start: Thread ID: 2316. Process Test2.exe (500)
Process Start: C:\Data\Embarcadero\PAserver\Administratör-Snotra-x32\Test2\Test2.exe. Base Address: $00400000. Process Test2.exe (500)
Module Load: Test2.exe. No Debug Info. Base Address: $00400000. Process Test2.exe (500)
Module Load: ntdll.dll. No Debug Info. Base Address: $76F60000. Process Test2.exe (500)

Breakpoint is overcrossed

---

Restart IDE

C++ console app with breakpoint
"Debug configuration - 32 bit Windows platform"
Target "32 bit Windows" (no profile, local debug)
Press F9

Thread Start: Thread ID: 8488. Process Test2.exe (7628)
Process Start: C:\Data\C++ Builder project\Test2\.\Win32\Debug\Test2.exe. Base Address: $00400000. Process Test2.exe (7628)
Module Load: Test2.exe. Has Debug Info. Base Address: $00400000. Process Test2.exe (7628)
Module Load: ntdll.dll. No Debug Info. Base Address: $76F80000. Process Test2.exe (7628)
…
Source Breakpoint at $0040120F: C:\Data\C++ Builder project\Test2\Test2.cpp line 15. Process Test2.exe (7628)

So, so the local debugger find the symbols, but the remote don't.
Read More...

Well, that's really odd because I have the opposite problem (community.embarcadero.com/index.php/foru...ith-remote-debugging) . I have a Win-7 x64 host running RAD Studio XE6, and I can set breakpoints on a Win-64 apps on a remote WIn-7 X64 host (symbols found). But I can't set breakpoints on the same app compiled for Win-32 when I debug it on a remote Win-7 x32 host, which you don't seem to have a problem with. Is that correct?
Read More...

If I rebuild the app for 64-bit Windows, and deploy it to a Windows 7 x64 sp1, with exactly the same PAserver configuration, then breakpoints work.

So there seems to be some problem in remote debugging of a Windows-32 app on a remote Windows-32 host from a Windows-64 host. Is this a know problem?
Read More...

Exactly the same problem (but occuring on C++Builder® 2007 R2) is described in Quality Central #61360 (qc.embarcadero.com/wc/qcmain.aspx?d=61360), and the solution is described as

Set the registry value „Disable Multiple Evaluators” in the Windows Registry under the hive
HKEY_CURRENT_USER\Software\Borland\BDS\5.0 Debugging\Borland Debuggers
from "1" to "0"

But I've checked HKEY_CURRENT_USER\Software\Embarcadero\BDS\14.0\Debugging\Embarcadero Debuggers\Disable Multiple Evaluators, and it's set to 0

So it seems like this is an old problem which really hasn't been taken care of properly. So the question is, has anybody managed to do get remote debugging with C++ app to work?
Read More...

Hi Dimitrij,
I assume that yoou've selected debug Build Configuration, and that Project/Options/C++ Options/Debug has Debug Information set to true.

I just created a VCL Form application, selected 64-bit Windows in Build Configuration, and added a line in TForm1::TForm1(TComponent* Owner) : TForm(Owner) to set a breakpoint at, and it worked fine.

May I recommend that you do the same, and then when you've got it working go from there?
BR
MatsW
Read More...

I have the following setup:

Local machine with RAD Studio XE6: Windows 7 x64 sp1 where I've build a 32-bit Windows app (app.exe)
Remote machine for debug: Windows 7 x86 sp1, PA-server running

Local machine setup with platform profile to remote machine, and deplayment works fine.

If I do Run/Load process/Local/Load then my app.exe loads on the local machine and I get a log saying that app.exe "Has Debug Info"

But if I can do Run/Load process/Remote/Load, then app.exe loads and starts on the remote machine, but the log says "No Debug Info" for app.exe even if the app.tds is in the same remote directory as app.exe

What magic is needed to get the remote rmtdbg to pick up the symbols from app.tds ?

Regards
MatsW
Read More...

Problem solved. The remote machine was a x64 version. When using a remote Win7-x86 then load works
Read More...

Hi,

I have a Win7-x64 running RAD Studio XE6 where I've built a C++ app. I then have a profile to a remote Win7-x32 machine where PAserver is running. The profile is selected under PLatform Manager/Target platform, and if I click "Test connection" then I get suceess back.


The button "Connected to remote host" in Deployment is active, and "Remote Status" shows "Same", so there connection works.


But when I try to Run/Load process.../Remote and set up for a Win32 Debugger, the remote host name, and app then I get "Unable to connect to remote host".


Are there some more ports that needs to be opened, or is there some other trick that needs to be done to get remote debugging to work?


Best regards


MatsW
Read More...