On Tue, Mar 16, 2010 at 5:34 PM, Diego Cantor-Rivera <[email protected]> wrote: > On 2:59 PM, OvermindDL1 wrote: > > On Tue, Mar 16, 2010 at 4:54 PM, Diego Cantor-Rivera > <[email protected]> wrote: > > > That is what I thought. I tried to check it manually but I didn't see > anything. Doesn't this file gets automatically generated when you run > cmake? (I have no idea) > > I am attaching it here. > > > Hmm, I did a quick look through it as well, looks fine. The fact that > it expects a < indicates a parsing error, but the error reporting does > not say 'where'... > > And yes, by default it is auto-generated. Hmm. You might step > through the parser and see where it fails and where it was in the > parsing stream, that would tell you where in the config file it is > dieing at... > > > > > I might do it ... if I knew where to look. My guess is somewhere in the > wthttp project?
Wt I think, however it is easier just to follow the call stack on down. Run the program, follow a few things down until you see crash, set new breakpoint right before there and restart and continue on down the call stack, usually does not take long (in Visual Studio anyway) and it locates the problem directly. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
