mikelui
commented
3 years ago 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.
when I use prism to trace the blackscholes of PARSEC, 4 thread, encounter this error: Sigrind: /home/l00515693/prism/src/Frontends/Gengrind/valgrind/sigrind/sigil2_ipc.c:78 (set_next_buffer): Assertion 'buf_idx == curr_idx' failed.
Both on X86 and ARM64 platform, the error ecountered.
So any bugs in Valgrind for PARSEC benchmark??
Detail information: bin/prism --backend=stgen -ltextv2 --executable=/home/l00515693/PARSEC-aarch64/bin/parsecmgmt -a run -p blackscholes -i simdev -n 4 [PRISM] [info] executable : /home/l00515693/PARSEC-aarch64/bin/parsecmgmt -a run -p blackscholes -i simdev -n 4 [PRISM] [info] frontend : default [PRISM] [info] backend : stgen [PRISM] [info] threads : 1 [PRISM] [info] timed : off [PRISM] [warning] '/home/l00515693/PARSEC-aarch64/bin/parsecmgmt': [PRISM] [warning] GCC version 4.9.2 not detected [PRISM] [warning] GCC version could not be detected [PRISM] [warning] OpenMP synchronization events may not be captured [PRISM] [warning] Pthread synchronization events are probably fine ==81125== Sigrind, ==81125== Copyright (C) 2015-2017, by Michael Lui et al. ==81125== Using Valgrind-3.15.0.GIT and LibVEX; rerun with -h for copyright info ==81125== Command: /home/l00515693/PARSEC-aarch64/bin/parsecmgmt -a run -p blackscholes -i simdev -n 4 ==81125== ==81125== ==81125== Beginning event generation from program start ==81125==
Sigrind: /home/l00515693/prism/src/Frontends/Gengrind/valgrind/sigrind/sigil2_ipc.c:78 (set_next_buffer): Assertion 'buf_idx == curr_idx' failed.
host stacktrace: ==81129== at 0x5801B73A: show_sched_status_wrk (m_libcassert.c:369) ==81129== by 0x5801B857: report_and_quit (m_libcassert.c:440) ==81129== by 0x5801B9E9: vgPlain_assert_fail (m_libcassert.c:506) ==81129== by 0x58014B97: vgSigrind_acq_event_slot (sigil2_ipc.c:78) ==81129== by 0x580147A0: vgSigrind_log_2I0D (log_events.c:65) ==81129== by 0x10031EA545: ??? ==81129== by 0x1002B26F2F: ??? ==81129== by 0x1002048BBF: ??? ==81129== by 0x1002B26F17: ??? ==81129== by 0x1002B26F2F: ??? ==81129== by 0x1002B26F3F: ??? ==81129== by 0x14713: ??? ==81129== by 0xEC11: ??? ==81129== by 0x10031EA4DF: ??? ==81129== by 0xEC11: ???
sched status: running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 81129) ==81129== at 0x5345B22: fork (in /lib/x86_64-linux-gnu/libc-2.27.so) ==81129== by 0x15FA87: make_child (in /bin/bash) ==81129== by 0x169561: command_substitute (in /bin/bash) ==81129== by 0x16E5C2: ??? (in /bin/bash) ==81129== by 0x16F885: ??? (in /bin/bash) ==81129== by 0x172CFA: ??? (in /bin/bash) ==81129== by 0x135A9A: ??? (in /bin/bash) ==81129== by 0x14E0D7: execute_command_internal (in /bin/bash) ==81129== by 0x14E00B: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81129== by 0x14DF47: execute_command_internal (in /bin/bash) ==81129== by 0x150A78: ??? (in /bin/bash) ==81129== by 0x136207: ??? (in /bin/bash) ==81129== by 0x14E0D7: execute_command_internal (in /bin/bash) ==81129== by 0x14FBF1: execute_command (in /bin/bash) ==81129== by 0x13A273: reader_loop (in /bin/bash) ==81129== by 0x138C7E: main (in /bin/bash) client stack range: [0x1FFEFFD000 0x1FFF000FFF] client SP: 0x1FFEFFE570 valgrind stack range: [0x1002A27000 0x1002B26FFF] top usage: 6912 of 1048576
Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks.
Sigrind: /home/l00515693/prism/src/Frontends/Gengrind/valgrind/sigrind/sigil2_ipc.c:78 (set_next_buffer): Assertion 'buf_idx == curr_idx' failed.
host stacktrace: ==81125== at 0x5801B73A: show_sched_status_wrk (m_libcassert.c:369) ==81125== by 0x5801B857: report_and_quit (m_libcassert.c:440) ==81125== by 0x5801B9E9: vgPlain_assert_fail (m_libcassert.c:506) ==81125== by 0x58014B97: vgSigrind_acq_event_slot (sigil2_ipc.c:78) ==81125== by 0x58014544: vgSigrind_log_comp_event (log_events.c:114) ==81125== by 0x1002F5649B: ??? ==81125== by 0x1002B26F2F: ??? ==81125== by 0x1002048BBF: ??? ==81125== by 0x1002B26F17: ??? ==81125== by 0x1002B26F2F: ??? ==81125== by 0x1002B26F3F: ??? ==81125== by 0x5846D89F: ??? ==81125== by 0xEAA2: ??? ==81125== by 0x10046BF30F: ??? ==81125== by 0xEAA2: ???
sched status: running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 81125) ==81125== at 0x52F8A10: free (in /lib/x86_64-linux-gnu/libc-2.27.so) ==81125== by 0x16E5E6: ??? (in /bin/bash) ==81125== by 0x16F885: ??? (in /bin/bash) ==81125== by 0x172CFA: ??? (in /bin/bash) ==81125== by 0x135A9A: ??? (in /bin/bash) ==81125== by 0x14E0D7: execute_command_internal (in /bin/bash) ==81125== by 0x14E00B: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x14DFD6: execute_command_internal (in /bin/bash) ==81125== by 0x14DF47: execute_command_internal (in /bin/bash) ==81125== by 0x150A78: ??? (in /bin/bash) ==81125== by 0x136207: ??? (in /bin/bash) ==81125== by 0x14E0D7: execute_command_internal (in /bin/bash) ==81125== by 0x14FBF1: execute_command (in /bin/bash) ==81125== by 0x13A273: reader_loop (in /bin/bash) ==81125== by 0x138C7E: main (in /bin/bash) client stack range: [0x1FFEFFD000 0x1FFF000FFF] client SP: 0x1FFEFFE800 valgrind stack range: [0x1002A27000 0x1002B26FFF] top usage: 6912 of 1048576
Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks.
[PRISM] [critical] Unexpected end of fifo