|
From: Pete V. <pv...@gm...> - 2004-12-10 21:00:19
|
Thanks for the response. It turns out I was being stupid and running Valgrind on my launch script rather than on the executable directly. Running the executable directly produced behavior that makes much more sense. Now a second newbie question -- if you're allowed more than one in a day. Do you have to do anything special to use Valgrind with UI's? After all its initialization and the reading of a project file, my app (a Qt app) dies when it seems it's about ready to start accepting user interactions. Since the error mentioned 'libc_freeres' in the trace, I added --run-libc-freeres=no to my options. Now the app dies without an error. Thanks again, Pete On Fri, 10 Dec 2004 10:31:02 -0800, Robert Walsh <rj...@du...> wrote: > > > > I'm a new user (downloaded Valgrind yesterday) and am wondering if > > anyone out there knows how to get VALGRIND_PRINTF to work. When I run > > my program under memcheck, I get logging output (at least when the > > program launches), but VALGRIND_PRINTF and VALGRIND_PRINTF_BACKTRACE > > don't seem to do anything. > > > > Could I be having problems because my application is built with the > > intel compiler and Valgrind was built with gcc? > > I'm guessing that's probably it. VALGRIND_PRINTF is a pretty ugly macro > that passes the varargs over to Valgrind for processing. If this > VA_LIST was generated with another compiler, then, if you're lucky, you > might some output. Most likely, everything go boom. > > I'm not too sure what to do about this, except maybe do the printf > processing in the macro and pass a fully-assembled string over. That's > ugly too, though. > > Regards, > Robert. > > |