On Thursday 15 April 2010 14:14:32 Josef Weidendorfer wrote: > Hi Milian, > > On Thursday 15 April 2010, Milian Wolff wrote: > > 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. > > Best is to file a bug report.
Even if I have no debug information at all? no backtrace, no useful debug out put ;-) That's why I thought I'd ask here first. > > How does one debug that? gdb -> valgrind -> app? > > In Valgrind sources, there is info about this in README_DEVELOPERS in the > toplevel directory. In addition to the info there, when starting the > tool executable in the debugger directly, one still also should provide > the "--tool=..." parameter in my experience. Hmm... should be added there. > > > That segfaults even earlier and gives a totally useless backtrace without > > any debug info... > > With callgrind, it could help to have the debug output produced by > --ct-verbose=... before the segfault. Do I need a newer callgrind/valgrind version for that? This option is not known in Valgrind 3.5.0 and I can't find anything in man valgrind either? Do you mean plain --verbose ? -- Milian Wolff [email protected] http://milianw.de
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ 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
