error in running parsec program using Valgrind frontend about prism

[mikelui]

Hi! Hiya! Hello! I'm back. I was away for a bit for internship and COVID nonsenses.

Back on development and maintenance again.

While I presume you've moved on from this issue, this is a problem Prism's valgrind has with shells that fork a binary.

The following ought to work (executing the direct binary):

bin/prism --backend=stgen -ltextv2 --executable="$PARSEC3DIR/pkgs/apps/blackscholes/inst/amd64-linux.gcc-pthreads/bin/blackscholes 4 $PARSEC3DIR/pkgs/apps/blackscholes/inputs/in_4.txt blackscholes.4thread.in_4.out"

You may need to untar the input file manually.

Supporting execution via the bash wrapper has been on the backburner for a bit, but wasn't a top priority because the workaround of directly executing the raw binary. I'll make another issue specifically for this.