We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello. I tried to run a 32-bit binary on an Ubuntu 16.04, which crashed with a SEGV instead.
System Details: Test on Ubuntu 16.04 LTS(x86_64)
Code:
//test.c #include<stdio.h> int main(){ int a; a=1; return 0; }
Command:
gcc -m32 ./test.c -o ./test ./build.py --arch i386 ./qasan ./test
QASAN Output:
QEMU-AddressSanitizer:DEADLYSIGNAL ================================================================= ==3414==ERROR: QEMU-AddressSanitizer: SEGV on unknown address 0x00008d413dfc (pc 0x00008d413dfc bp 0x0000ffffdb49 sp 0x0000ffffdadc T3414) #0 0x00008d413dfc #1 0x0000ff7cf871 in strstr (/home/spiderman/qasan_32/libqasan.so+0x3871) QEMU-AddressSanitizer can not provide additional info. SUMMARY: QEMU-AddressSanitizer: ==3414==ABORTING qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault (core dumped)
Probably QASAN_LOAD leads to it.
QASAN_LOAD
By the way, I got no problem running this binary on qasan-qemu. Do you have any idea?
The text was updated successfully, but these errors were encountered:
Ubuntu 16.04 is too old and has a not supported libc. See #10 for the workaround.
Sorry, something went wrong.
Ok this is confirmed also with 18.04, it is a regression due to the refactoring of the backdoor code. Just pushed an hotfix ac0e38c
No branches or pull requests
Hello.
I tried to run a 32-bit binary on an Ubuntu 16.04, which crashed with a SEGV instead.
System Details:
Test on Ubuntu 16.04 LTS(x86_64)
Code:
Command:
QASAN Output:
Probably
QASAN_LOAD
leads to it.By the way, I got no problem running this binary on qasan-qemu. Do you have any idea?
The text was updated successfully, but these errors were encountered: