By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,958 Members | 1,179 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,958 IT Pros & Developers. It's quick & easy.

built dll in release mode, adding event log entries referencing code

P: n/a
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
Jul 22 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"Idelso Quintero" <id*************@insurance.sungard.com> wrote in message
news:61**************************@posting.google.c om...
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


You seem to be way off topic here, this is a group about the C++ language.

I suggest you ask again on a group either about Windows or about the Visual
C++ compiler. For instance news:comp.os.ms-windows.programmer.win32 or
news:microsoft.public.vc.language

john
Jul 22 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.