   COLLADA DOM problem
  I'm trying to set up a basic importer from COLLADA to my engine internal format but there are problems with the loading routines. I use COLLADA DOM. Here's my code:1st attempt (caused crash - segmentation fault or similar):DAE *collada_dom = new DAE();daeInt error = collada_dom->load("file:///C:/knight.dae");2nd attempt (pure guessing, this time no crash, but this time I got an error message printed to console):DAE *collada_dom = new DAE();char buffer[1000];daeInt error = collada_dom->load("file:///C:/knight.dae", buffer);The error message from the 2nd attempt was:file:///C:/knight.dae:1: parser error : Document is empty[a long sequence of about two rows of odd characters here...]^Error: daeLIBXMLPlugin::read(knight.dae) failed - XML Parse FailedI already verified that this file was non-empty, and that it could be opened correctly by this COLLADA loader:http://www.gamedev.net/community/forums/topic.asp?topic_id=450761The file I tried to open was the file knight.dae which comes with the binaries package for that COLLADA loader.Why can't it load the file and how can I fix it?   
  Have you tried the filename without the prefix, i.e. just "C:/knight.dae" ?;  It didn't work :/By the way, don't you think it's odd with the "buffer" parameter? Just sending the pointer to any memory I have allocated, of any size I happen to have chosen... It doesn't make sense... Shouldn't the method call WITHOUT setting the 2nd parameter work without a segmentation fault?   ;  Firstly I'd make sure the same thing happens with a minimal program that just tries to load the file and does nothing else.I know nothing about Collada, but the fact that it crashes unless you put a big buffer on the stack suggests very strongly that the load code is buggy. It's probably declaring a fixed sized array on the stack somewhere and accessing it using an out of range index.If you have access to that load code try building a debug version and putting the stack checking on in the code generation options (I think it's on by default in debug anyway). That will probably help you work out more precisely where the bug is.   ;  Hm, I think I solved it now (not sure yet), but the buffer seems to not be an output buffer, but an input buffer. I wrote a small fileToMemory function, and passed the returned pointer to the function. Now I get neither crash nor error message. It seems like I can type whatever I like in the char * argument of the load function, and that this will be used as document id in the collada dom system, and not necessarily has to be the filename.   