I
Idelso Quintero
Hi everyone:
Hopefully someone has experienced this strange behavior before. I have
an application's dll that is failing when certain input is entered. We
know about it and are working on it. What is really weird is the
description that is being added to the event log when the dll fails.
It is mentioning specific .cpps (with directory location) and the line
of code that is failing. Important to mention that the application is
running on a server, not the development machine and the event log
entry mentions directory information in the development machine. In
other words it is behaving as if debugging symbols/information is kept
in the dll, but as i said at the beginning, this dll is being compiled
in released mode. Any idea if there is any specific hidden option in
Visual C++, that might need to be turn on/off to avoid this.?
Any help will be greatly appreciated.
Idelso
Hopefully someone has experienced this strange behavior before. I have
an application's dll that is failing when certain input is entered. We
know about it and are working on it. What is really weird is the
description that is being added to the event log when the dll fails.
It is mentioning specific .cpps (with directory location) and the line
of code that is failing. Important to mention that the application is
running on a server, not the development machine and the event log
entry mentions directory information in the development machine. In
other words it is behaving as if debugging symbols/information is kept
in the dll, but as i said at the beginning, this dll is being compiled
in released mode. Any idea if there is any specific hidden option in
Visual C++, that might need to be turn on/off to avoid this.?
Any help will be greatly appreciated.
Idelso