DLL breakpoints do not fall into the "remote debugging symbols" options, why and any security risks with them?

I had a big problem with the fact that breakpoints did not hit the Delphi 6 DirectShow DLL. I would load the DLL (AX) into the IDE and run it using Graph Edit as the host program, and none of the breakpoints would start. I tried moving the FastMM4 library to the project directory, completely uninstalling FastMM4, turning debugging DCU on and off, cleaning up project directories, unregistering and re-registering the DLL, all I could think of. Nothing succeeded. Each time I ran the host program, I saw my DLL load with the message “No debugging information” in the event viewer. Then, in a desperate Google search, I found a message for C ++ Builder, in which it is recommended to try the link "deleted debugging symbols":

Project -> Options -> Linker (Tab) -> Exe and DLL options (group box) -> "Enable Remote Debugging Symbols" (checked)

Suddenly, my control points began to hit. Here are my questions:

1) Why does it work? Is it because of the option or because this option activated some other compiler / linker operations that fixed things? I would like to know, so I can reliably fix this problem in the future when it happens again.

2) Are remote debugging symbols something of a hostile programmer for deeply tracking my program? In other words, are they a security risk when lying around?

+5
source share
1 answer

1) - . IDE , . Debug DCU - VCL DCU, , . : Delphi DCU .

2) / , , , - . .

, , , .

+5

All Articles