|
From: Yeshurun, M. <mei...@in...> - 2005-08-17 12:30:39
|
Do you get a segfault when breaking printf's replacement and not touching fprintf's replacement? (There's a very good change printf calls fprintf). -----Original Message----- From: Rob Holland [mailto:ti...@ge...]=20 Sent: Wednesday, August 17, 2005 3:25 PM To: Yeshurun, Meir Cc: valgrind-users Subject: Re: [Valgrind-users] RE: Replacing printf On Wed, 2005-08-17 at 14:51 +0300, Yeshurun, Meir wrote: > I could be wrong of course. Perhaps you could try to make Valgrind > generate an error for printf by passing weird arguments, and then check > in the stack trace if printf is in a.out or in a so. If it's in a so, it > would definitely rule out what I suggested. Good idea. Interestingly, if I deliberately break my (f)printf replacements, they both segfault. So my code _is_ being run here it seems. So I'm a bit lost as to why it appeared not to work before. Thanks for the tip, looks like I was barking up the wrong tree :/ Cheers, Rob --=20 |