FS#54939 - [valgrind] sends 32-bit programs under test SIGILL
Attached to Project:
Community Packages
Opened by David Phillips (phillid) - Thursday, 27 July 2017, 00:08 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 27 January 2018, 18:59 GMT
Opened by David Phillips (phillid) - Thursday, 27 July 2017, 00:08 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 27 January 2018, 18:59 GMT
|
Details
Description:
Attempting to test a 32-bit program with valgrind from [multilib-testing] will result in valgrind giving the attached output. It complains about unhandled instruction bytes. When the program under test is a 64-bit program, valgrind appears to behave itself nicely. Additional info: * valgrind-multilib 3.13.0-2 from [multilib-testing] * Program under test compiled with gcc-multilib 7.1.1-4 Steps to reproduce: A simple, self-contained test case is to run `echo "int main(int argc, char* argv[]){}" | gcc -m32 -x c - && valgrind ./a.out`. I have tested against valgrind-multilib valgrind-multilib 3.13.0-1 and gcc-multilib 7.1.1-4, and the issue is not present. |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Saturday, 27 January 2018, 18:59 GMT
Reason for closing: Fixed
Saturday, 27 January 2018, 18:59 GMT
Reason for closing: Fixed
EDIT: I should clarify that I built valgrind-multilib with the -fno-plt flag included.