Maybe --trace-syscall=yes may help to figure out the problem? HTH, ALex
On Thu, Apr 15, 2010 at 3:45 PM, Milian Wolff <[email protected]> wrote: > Hey all! > > When I try to profile the whole startup of KDevelop using callgrind, I and at > least one of the other developers, get a reproducible segfault. This does not > occur in memcheck or massif, so I fear it shows a bug in callgrind itself. > > How does one debug that? gdb -> valgrind -> app? > > That segfaults even earlier and gives a totally useless backtrace without any > debug info... > > Hints? > -- > Milian Wolff > [email protected] > http://milianw.de > > ------------------------------------------------------------------------------ > 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 > _______________________________________________ > Valgrind-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/valgrind-users > > -- Alexander Potapenko Software Engineer Google Moscow ------------------------------------------------------------------------------ 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 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
