Bug 473938
Summary: | glibc-debuginfo wrong on s390x | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Petr Muller <pmuller> |
Component: | glibc | Assignee: | Andreas Schwab <schwab> |
Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE <qe-baseos-auto> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | fweimer, jakub, jan.kratochvil, ohudlick |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | s390x | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-08-25 08:31:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Muller
2008-12-01 15:04:17 UTC
In what way is the .symtab wrong? pause and __pause_nocancel functions really overlap in the code, the .symtab correctly describes that. The instruction at 0xaffc2 (svc==syscall) is really used during execution but 0xaffc2 does not belong to any function according to .symtab on s390x. Any overlapping would be OK but for all the functions either {function start} + {function size} < {syscall PC} or {syscall PC} < {function start} x86_64 is correct. On s390(x) the real body of canceable syscalls is actually located _before_ the entry point. Thus the pc is actually in the nanosleep syscall (162 == SYS_nanosleep). Not really a bug, since the pc is inside an anonymous function. |