On Tue, Apr 24, 2012 at 11:45 AM, Julian Seward <[email protected]> wrote: > > Maybe the &s or some other characters in the command line arguments > are not getting handled properly by the shell?
in bash: $ echo "a&b" a&b $ echo 'a&b' a&b $ echo a&b [1] 4711 <- Process ID of background process "echo a" a <- Result of "echo a" bash: b: command not found <- bash complains [1]+ Done echo a <- "echo a" has terminated $ echo a\&b a&b Unfortunately, if you are calling valgrind by a shellscript (not unpopular due to the length of the command), the escaping varies a little. Better you try out yourself in the script. regards, Manuel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
