Is Profiling Useless in Today's World?
rngadam writes "gprof doesn't work in Linux multithreaded programs without a workaround that doesn't work that well. It seems that if you want to use profiling, you have to look for alternatives or agree with RedHat's Ulrich Drepper that "gprof is useless in today's world"... Is profiling useless? How do you profile your programs? Is the lack of good profiling tools under Linux leading us in a world of bloated applications and killing Linux adoption by the embedded developers? Or will the adoption of a LinuxThreads replacement solve our problems?"
Why can't my code be judged by the content of its characters, and not by the color of its extension?
:)
Down with profiling!
Me: Really? Which part?
User: When I click the "report" icon
Me: Oh (tinkers with report code). Try it now.
User: It's still slow
Me: (shakes BOFH excuse 8-ball) Hrmm, must be interference from sunspots, try it again tommorrow
Today I didn't even have to use my AK; I got to say it was a good day -- Icecube
Most, if not all, ./ readers have never written a line of code more involved than 10 print "hello". They spend their time trying new enlightnement and gnome themes and rebooting into windows 98 to play games and post to slashdot (since they can't figure out how to configure pppd).