|
From: Nicholas N. <nj...@ca...> - 2003-11-17 14:39:53
|
On Mon, 17 Nov 2003, Massimo Narizzano wrote: > I have runned valgrind on my code and I have obtained a couple of > error before a segmentation fault. > Everything works fine except the fact that valgrind shows me > that there are some errors in my code but not which line they are. > It may be the case that the error line is too long and it is not > shown entirely. > Does exist an option that say how to increment the lenght of the error > lines? No option, but you can change the value of M_VG_ERRTXT (in coregrind/vg_include.h) and recompile. We should handle that better. > You can also find in attach an example of how the lines are cutted. > __________________________________________________ > =6336== Conditional jump or move depends on uninitialised value(s) > ==6336== at 0x805616B: > ConstraintPropagation<ComposeData<Typelist<AtomsData, > Typelist<ConstraintsData<WatchThreeLiteralsSupport>, > Typelist<LookAheadData, Typelist<AssignmentsData, > Typelist<ConflictsData, Typelist<SolutionsData, > Typelist<ConstraintsToBeLearnedData, > Typelist<ComposeData<Typelist<BacktrackingStatisticsData, > Typelist<LearningStatisticsData, NullType> > >, > Typelist<ElementsData<StdAllocator>, NullType> > > > > > > > > >, > QbfSolver::Dispatcher_, > WatchThreeLiteralsSupport>::outOfLevelExistSimplificatio Wow, you really like templates, huh? :) N |