   TinyXML problems
  Greetings, i have exhausted many possibilites and spent many countless hours as a solution to this problem. The situation is Im using Tiny XML to quite an extent of success, i have files loading, in and out no problem...As long as its compiled on my room mates computer. Any other computer it compiles but has an execution error saying that the project settings are not configured properly, and i narrowed it down. It occurs the minute i use any of tinyXML functionality e.g the minute i use  "TiXmlElement root = LoadXML(XmlFilename);" it comes up with this error, on nearly every other com ive tested with the exception of my room mates. Other than that my program runs fine, of course without any images, or animation frames as this is what im using xml for. i'm also getting these warnings if this will aid you in a solution. cheers.1>tinyxml-debug.lib(tinystr.obj) : warning LNK4099: PDB 'vc80.pdb' was not found with '..\Includes\Win32_L\tinyxml-debug.lib' or at 'k:\B3n\Angry MKIII\Output\Debug\vc80.pdb'; linking object as if no debug info1>tinyxml-debug.lib(tinyxml.obj) : warning LNK4099: PDB 'vc80.pdb' was not found with '..\Includes\Win32_L\tinyxml-debug.lib' or at 'k:\B3n\Angry MKIII\Output\Debug\vc80.pdb'; linking object as if no debug info1>tinyxml-debug.lib(tinyxmlerror.obj) : warning LNK4099: PDB 'vc80.pdb' was not found with '..\Includes\Win32_L\tinyxml-debug.lib' or at 'k:\B3n\Angry MKIII\Output\Debug\vc80.pdb'; linking object as if no debug info1>tinyxml-debug.lib(tinyxmlparser.obj) : warning LNK4099: PDB 'vc80.pdb' was not found with '..\Includes\Win32_L\tinyxml-debug.lib' or at 'k:\B3n\Angry MKIII\Output\Debug\vc80.pdb'; linking object as if no debug info   
  Have you delivered the pdb's, too? If I understand the documentation of Microsoft right VC80.pdb just stores the debuginfos regarding the several object files and must located in the same directory as the lib ( see MSDN-Docu ). Maybe you should doublecheck this.Kimmi   ;  Ive looked around a bit more and theres talk about keeping your .lib and .pdb consistant, and generated from the same building process. I'm not entirely sure how to proceed to do this.   ;  If you are building the library in debug mode, Visual studio is generating pdb-files with the debuginfos like types of used data, Names of function / methods and similar stuff. Normally you can locate this stuff in your output directory. If you want to debug a library the pdbs must be generated in the same build as the library / dll which you are using to make sure, that you can debug it correctly. If you are debugging the debugger searches for those files in the working directory of your debugging session ( see properties -> Debugging -> working directory ). Make sure that your generated pdbs are locates in this directory or adapt it to the path to your executable, which you are currently debugging.KimmiP.S.: If I explainted it too complicated, just ask again :-)...;  I get The general gist of it, and thank you for being so thorough, and upon checking everything seems in order the PDB are being generated in the debug folder along side the executeable. However it continue's to insist that upon compiling correctly that the project configuration's are wrong. Yet i can take it back home and put it on my rom mates computer right now and it will work.....sighedit: i Double checked and found that the vc08 file was not located in the output\debug as you said it should have been. Alas new warnings has appeared1>tinyxml-debug.lib(tinystr.obj) : warning LNK4204: 'k:\B3n\Angry MKIII\Output\Debug\vc80.pdb' is missing debugging information for referencing module; linking object as if no debug info1>tinyxml-debug.lib(tinyxml.obj) : warning LNK4204: 'k:\B3n\Angry MKIII\Output\Debug\vc80.pdb' is missing debugging information for referencing module; linking object as if no debug info1>tinyxml-debug.lib(tinyxmlerror.obj) : warning LNK4204: 'k:\B3n\Angry MKIII\Output\Debug\vc80.pdb' is missing debugging information for referencing module; linking object as if no debug info1>tinyxml-debug.lib(tinyxmlparser.obj) : warning LNK4204: 'k:\B3n\Angry MKIII\Output\Debug\vc80.pdb' is missing debugging information for referencing module; linking object as if no debug info   ;  Is Visual Studio installed in your roommates' computer?I really doubt the missing PDB files have anything to do with your problem, because these files are used when using the debugger to show where in the code you are when a break occurs or when stepping line by line (among others.)The error message you described sounds a lot like the visual studio run time is not installed in those machines where the error happens.  Are you just copying the executables plus resources?  Or are you using an installed that also installs the runtime?As a quick test, you can install the visual studio 8.0 runtime redistributable from Microsoft to the computers where the application won't run.  It also is installed somewhere in you visual studio's directory (as are the merger modules to use in a MSI installer.)Keep in mind that you need to compile the executables in release mode otherwise you could only run the applications on computers that have Visual Studio installed.   ;  Maybe you mixed up relead and debug builds ( your tinyxml-build seems to be a debug build ). And make sure that the linked runtime is the same ( doublecheck the properties C/C++ -> Code generation -> Runtime Library ).Kimmi;  well the problem was first encountered on my PC, after a few hours of trying to get it to work i had the whimsical idea that maybe it was my computers fault as unlikely as it was, hence me trying it on my friends computer, however all i copied over is the executeable plus resources and it worked on his however no where else. And as for visual studio 8.0 runtime redistributable, do i just intall it and then attempt to compile and run my project again or is it a little more complex then that?   ;  Open the tinyXML project you are using and check if the following settings are set:C/C++, General, Debug Information Format: Zi or ZILinker, Debuggin, Generate Debug Info: Yes (/DEBUG)Probably one of them is not set and this makes Visual Studio complain about missing debugging information (by the way, it is no error but a warning ;))However those PDBs are NOT needed to run the programm. They are only of interest when you attach a debugger to the program (the debugger then tries to load the dll along with the pdb).But this should not be the problem of your crash.As others have said, the computer it crashes on is missing a needed dll. It could be a missing visual c runtime.   ;  If you have the visual studio runtime redistributable on the computers it should normally work. You can just check your application using depends to verify your app ( just google for it ), that program can show you the missing dlls / libs.KimmiP.S.: Sorry for my confusing answers at first. I thought you just had issues to debug your application on a different computer.   