ltrace is throwing segfault while running any of the userspace command
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ltrace (Ubuntu) |
Fix Released
|
High
|
Mathieu Trudel-Lapierre | ||
Trusty |
Incomplete
|
Low
|
Mathieu Trudel-Lapierre | ||
Wily |
Won't Fix
|
Low
|
Mathieu Trudel-Lapierre |
Bug Description
[Impact]
ppc64el users of ltrace.
[Test cases]
- ltrace `which ls`
- ltrace /bin/ls /usr
- ltrace ps
- ltrace make (building ltrace itself, for instance)
[Regression potential]
While the changes should fix some of the more common uses of ltrace, the added/modified methods and options may break for some specific calls on ppc64el, or on other architectures (powerpc, arm) which are affected by the changes.
ARM was already failing with the available version of ltrace; this would not change the behavior on ARM.
---
== Comment: #0 - Praveen K. Pandey <email address hidden> - 2016-01-25 01:18:25 ==
Hi ,
I Installed Ubuntu16.04 In PowerNV and try to run ltrace ls or ltrace ps it will fail with segfault .
Reproducible Step :
1- Install Ubuntu16.04 in PowerNV or as KVM or as PowerVM
2- Install ltrace package
3- Try to run ltrace with any userspace utility like "ltrace ps"
Actual Result :
Throw Seg fault
Expected :
LOG
root@lep8d:~# uname -a
Linux lep8d 4.3.0-7-generic #18-Ubuntu SMP Tue Jan 19 15:47:35 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
root@lep8d:~#
root@lep8d:~# ltrace ps
__printf_chk(1, 0x3fffe4d40028, 0x3fffe4d40038, 0x3fffe4d400e0 <unfinished ...>
qsort(0x10017850, 0, 0, 0x3fffe4d400e0) = <void>
__gmon_
ferror(0x6) = 230428656
__libc_
readproctab3(
uptime(
__fpending(
strrchr("\037 !"#$%&'
escape_
setlocale(
select(1, 0x40087468, 0x3fffe4d3fa00, 0) = 1
__xstat(268534584, "\017", 0x13) = 0
strncmp("", "unknown", 7) = -455870136
sigfillset(
getpagesize() = 6
meminfo(0, 0x100182d0, 0, 0) = 0
getpagesize( <unfinished ...>
__stack_chk_fail(0, 0x100182d0, 0, 0 <no return ...>
--- SIGSEGV (Segmentation fault) ---
strncpy(0, "Signa", 5) = 0x10017da8
dlerror() = "SEGV"
strcmp("\206 \255\373", "\001\002\
) = 58
readtask(0, 0, 0x10017de8, 66ps:display.c:66: please report this bug
) = 0
__snprintf_chk(11, 0, 0x3fff81c5175b, 0) = 0x10003e90
time(0x10003e90) = 30039
fork() = 0
unexpected breakpoint at 0x3fff81b339a4
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
root@lep8d:~#
== Comment: #7 - Thierry Fauck <email address hidden> - 2016-02-17 14:11:52 ==
The problem is related to procps-ng 3.3.10
Upgrade to procps-ng 3.3.11 solves the issue
Going to Mirror and ask Canonical to advise.
== Comment: #9 - Thierry Fauck <email address hidden> - 2016-02-17 14:13:10 ==
This bugs is linked to procps-ng 3.3.10 known as having some issues. Is upgrade to 3.3.11 an option ?
tags: | added: architecture-ppc64le bugnameltc-135982 severity-high targetmilestone-inin1604 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | procps (Ubuntu) → ltrace (Ubuntu) |
Changed in ltrace (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Mathieu Trudel-Lapierre (cyphermox) |
Changed in ltrace (Ubuntu): | |
importance: | Undecided → High |
status: | Incomplete → Triaged |
Changed in ltrace (Ubuntu): | |
status: | Triaged → In Progress |
description: | updated |
Changed in ltrace (Ubuntu Trusty): | |
status: | New → In Progress |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
importance: | Undecided → High |
Changed in ltrace (Ubuntu Wily): | |
importance: | Undecided → High |
Changed in ltrace (Ubuntu Trusty): | |
importance: | High → Low |
Changed in ltrace (Ubuntu Wily): | |
importance: | High → Low |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
Changed in ltrace (Ubuntu Trusty): | |
status: | In Progress → Incomplete |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1547152/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]