Hi, I've encountered the same problem than the one reported in the message "gmane.comp.debugging.valgrind:8859", i.e. that --log-file=xxx%p does not work when there is a fork and no exec. The argument to create the new log file only at exec time was that it was an uncommon programming situation. Well, I have a use case for that, because I teach system programming and there are cases when one wants to have forks and no execs. So, would it be possible to change the behaviour of the --log-file option or at least to make that the ==xxx== pattern that prefix all ouput lines contains the actual PID and not always the one of the parent process ?
Best regards, Sébastien Paumier ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
