|
Please post compilable code snippet and array declaration. I hope you've enabled project settings to debug in release mode or else the compiler will show bogus values.
Regards,
Jijo.
_____________________________________________________
http://weseetips.com[ ^] Visual C++ tips and tricks. Updated daily.
|
|
|
|
|
I can show you the full code of this function tomorrow. Actually I am checking the values by writing the values into a text file in both modes.
-thanks
PKNT
|
|
|
|
|
You've initialized data, but have you initialized other variables like sqrt_x?
Nibu babu thomas
Microsoft MVP for VC++
Code must be written to be read, not by the compiler, but by another human being.
Programming Blog: http://nibuthomas.wordpress.com
|
|
|
|
|
Ofcourse I did, orelse, how can I get correct result while executing the the debug version of the application  ??
PKNT
|
|
|
|
|
|
thanks for the link. I did exactly what he said under section "Making Debug Mode more like Release Mode" and it did the trick and now its works fine.
PKNT
|
|
|
|
|
In my experience differences in Debug and Release mode occurs when there a bug in the program, typically pointer related. Most likely some other part of your program is over writing the "data" array. One way to quickly handle such problmes is to selectively comment code and find out which section of code is creating problem.
-Saurabh
|
|
|
|
|
I'm updating an old (32bit) command line C++ program that I used to detect specific human input devices connected to the USB port.
the includes for this project are:
extern "C"
{
#include "hidsdi.h"
#include "hidusage.h"
#include "hidpi.h"
}
the project compiles without linking error as a 32bit application.
However, as soon as I switch to 64bit I get linker errors such as:
Error 1 error LNK2019: unresolved external symbol HidD_FreePreparsedData referenced in function "public: __cdecl DgCpDfuFunctions::~DgCpDfuFunctions(void)" (??1DgCpDfuFunctions@@QEAA@XZ) DgCpDfuFunctions.obj
Error 2 error LNK2019: unresolved external symbol __imp_SetupDiDestroyDeviceInfoList referenced in function "private: int __cdecl DgCpDfuFunctions::FindControlPanel(struct _hidDeviceStruct *)" (?FindControlPanel@DgCpDfuFunctions@@AEAAHPEAU_hidDeviceStruct@@@Z) DgCpDfuFunctions.obj
Error 3 error LNK2019: unresolved external symbol __imp_SetupDiGetDeviceInterfaceDetailA referenced in function "private: int __cdecl DgCpDfuFunctions::FindControlPanel(struct _hidDeviceStruct *)" (?FindControlPanel@DgCpDfuFunctions@@AEAAHPEAU_hidDeviceStruct@@@Z) DgCpDfuFunctions.obj
Error 4 error LNK2019: unresolved external symbol __imp_SetupDiEnumDeviceInterfaces referenced in function "private: int __cdecl DgCpDfuFunctions::FindControlPanel(struct _hidDeviceStruct *)" (?FindControlPanel@DgCpDfuFunctions@@AEAAHPEAU_hidDeviceStruct@@@Z) DgCpDfuFunctions.obj
I made sure that the 64bit "project properties" -> "Linker" -> "Input" are set up exactly like the 32bit project.
Note: I'm using the libraries from the Windows DDK, i.e. \lib\wxp\i386\hid.lib
EDIT: I'm using Visual Studio 2005
modified on Wednesday, June 18, 2008 1:43 PM
|
|
|
|
|
abiemann wrote: Note: I'm using the libraries from the Windows DDK, i.e. \lib\wxp\i386\hid.lib
I am not sure about the problem but it seems that you are linking with 32-bit version of the library. Do you have a folder with x64 or IA64 in the lib folder.
-Saurabh
|
|
|
|
|
I tried the IA64 folder... but then I see this error:
hid.lib(HID.DLL) : fatal error LNK1112: module machine type 'IA64' conflicts with target machine type 'x64'
NOTE:
this is my x64 debug configuration (preprocessor)
_DEBUG
WIN64
_CONSOLE
WINVER=0x0501
_CRT_SECURE_NO_WARNINGS
_CRT_SECURE_NO_DEPRECATE
modified on Wednesday, June 18, 2008 6:37 PM
|
|
|
|
|
IA64 is Itanium. x64 is AMD64 (and EM64T - Intel's implementation of AMD64).
The target market for Itanium is tiny because Itanium was a colossal failure. If you use a processor like an Athlon, Opteron, Xeon, Core 2, Core i7 and so on, it will be using x64 (AMD64/EM64T). If you buy 64bit Windows (such as XP 64 bit or Vista 64 bit) it will be x64.
You can't use IA64 on an x64 platform, so you need the x64 (probably labelled AMD64) versions of these libs, not the IA64 ones, which is exactly what the first error says.
I can't find these either (I only have x86 no matter what I try to install) so if you find/have found these 2 libs, please let me know 
Never mind, found it.
modified on Wednesday, December 3, 2008 7:12 PM
|
|
|
|
|
Hello community,
i try to debug a little project downloaded here from codeproject and if i want to start them i recive this message:
Debugging information for "explorer.exe" cannot be found or does not match.
and i cannot set any breakpoints!
Can someone help me here to solve this, are there any settings to set?!
Thanks for any help!
termal
|
|
|
|
|
termal wrote: a little project downloaded here from codeproject
which project?
|
|
|
|
|
|
Most probably you might be debugging in release version. Since release version don't have debug informations by default, you can't debug it.
So options are
1) Debug in debug version.
2) Enable debug information in release version. For that take project settings and
a) Set C/C++ > Optimization as "disabled"
b) Set C/C++ > Debug Info as "Program Database"
c) Enable Link > Generate Debug Info.
Regards,
Jijo.
_____________________________________________________
http://weseetips.com[ ^] Visual C++ tips and tricks. Updated daily.
|
|
|
|
|
Hello,
thanks for answer, i have already make this settings but still the same, i try this in debug mode with VS8
regards
termal
|
|
|
|
|
Debugging a shell extension is different then debugging other applications. For shell extensions you have to debug explorer.exe since it loads the shell extension. You cannot debug explorer.exe at the source level since it is part of OS and its source code is not available.
To get debugging symbols use symbol server to get the symbols for system binaries. You can read more about symbol server at here[^].
To configure symbol server in VS 2008 follow these steps:
1. Tools->Options->Debugging->Symbols
2. Under symbol files(.pdb) locations add an entry containing http://msdl.microsoft.com/download/symbols.
3. In cache symbols from ... give a path to save the symbols locally.
Also you will find lots of information if you google "debugging shell extensions".
-Saurabh
|
|
|
|
|
Hello,
thank you very much for your information!!
best regards
termal
|
|
|
|
|
You are welcome.
-Saurabh
|
|
|
|
|
I'm writing a program to record window activities but I just can save in AVI format. I would like to convert it to WMV format. Some one plz help me ![Rose | [Rose]](https://www.codeproject.com/script/Forums/Images/rose.gif)
|
|
|
|
|
capint wrote: I would like to convert it to WMV format. Some one plz help me
I dug real deep and found this.
"Love people and use things, not love things and use people." - Unknown
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
 R u present me a software to convert. I would like to use MFC to do that 
|
|
|
|
|
The Windows Media Format SDK (download here[^]) handles Windows Media files.
Mark
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://www.codeproject.com/script/Forums/Images/coffee.gif)
|
|
|
|
|
I am getting an windows exception
001B:7C16E14F Ordinal1028+7D
Anybody help me to understand what is Ordinal 1028?????????
|
|
|
|
|
Using the debugger, you should be able to see what DLL is mapped into the address space shown in the exception and/or call stack.
Use a tool like DUMPBIN dump the exports from that DLL and you will be able to find out what exported function is causing the problem.
Note sure that will help you much, though...
Peace!
-=- James Please rate this message - let me know if I helped or not!<hr></hr>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
