Hi,

today I encountered a problem which I have not solved yet, and I'm not 
sure if the problem is in Gecode or in my code. In disassembly code, I 
saw what seemed as a quite tight infinite loop somewhere in 
GecodeKernel.dll. What I would like is to get a pdb file so that the 
Visual C++ debugger correctly sees the call stack. Is there a 
recommended way of obtaining the pdb files? I think that it's necessary 
to pass "/DEBUG /PDB:"GecodeKernel.pdb" to link.exe for the release 
build. (This IMHO does not change the dll files themselves, it just 
creates appropriate pdbs and thus enables debugging.)

Thanks,
Filip


_______________________________________________
Gecode users mailing list
[EMAIL PROTECTED]
https://www.gecode.org/mailman/listinfo/gecode-users

Reply via email to