| Summary: |
SIGILL documentation: compiler generates invalid instructions |
| Product: |
[openSUSE] openSUSE Tumbleweed
|
Reporter: |
Christopher Yeleighton <giecrilj> |
| Component: |
Development | Assignee: |
E-mail List <screening-team-bugs> |
| Status: |
RESOLVED
NORESPONSE
|
QA Contact: |
E-mail List <qa-bugs> |
| Severity: |
Normal
|
|
|
| Priority: |
P5 - None
|
CC: |
chcao, giecrilj, kaykaykay123
|
| Version: |
Current | Flags: |
chcao:
needinfo?
(giecrilj)
|
| Target Milestone: |
--- | |
|
| Hardware: |
x86-64 | |
|
| OS: |
openSUSE Tumbleweed | |
|
| URL: |
info:/libc/Program Error Signals
|
| See Also: |
https://bugzilla.opensuse.org/show_bug.cgi?id=1212101
|
| Whiteboard: |
|
|
Found By:
|
Community User
|
Services Priority:
|
|
|---|
|
Business Priority:
|
|
Blocker:
|
---
|
|---|
|
Marketing QA Status:
|
---
|
IT Deployment:
|
---
|
|---|
The documentation for Macro: int SIGILL in 24.2.1 Program Error Signals contains the following outdated claim: > Since the C compiler generates only valid instructions, ‘SIGILL’ typically indicates that the executable file is corrupted, or that you are trying to execute data. Unfortunately, this assurance is not true any more. The text should be fixed in the following way: ‘SIGILL’ typically indicates that the executable file has been compiled for a newer machine than the one the code is being executed on. It may also mean that that the executable file is corrupted, or you are trying to execute data.