Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#27250 - [ltrace] SIGSEGV due to int3 right after a call instruction
Attached to Project:
Arch Linux
Opened by Manuel Bovo (jackbit) - Friday, 25 November 2011, 13:53 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 15 January 2012, 16:35 GMT
Opened by Manuel Bovo (jackbit) - Friday, 25 November 2011, 13:53 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 15 January 2012, 16:35 GMT
|
DetailsDescription:
The execution of an int3 instruction immediately following a call instruction will crash ltrace with a SIGSEGV. Additional info: * ltrace 0.5.3-2 * tested on x86_64 * see Debian bug 649569 -> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649569 Steps to reproduce: echo 'main(){puts("");asm("int3");}'|gcc -oa -xc -;ltrace ./a; See Debian bug 649569 for more info. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649569 |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Sunday, 15 January 2012, 16:35 GMT
Reason for closing: Fixed
Additional comments about closing: See comment #1.
Sunday, 15 January 2012, 16:35 GMT
Reason for closing: Fixed
Additional comments about closing: See comment #1.
Now it doesn't segfault but instead hangs; is this the correct behavior of int3?