Bug 1212610 - SIGILL documentation: compiler generates invalid instructions
Summary: SIGILL documentation: compiler generates invalid instructions
Status: RESOLVED NORESPONSE
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Development (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL: info:/libc/Program Error Signals
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-22 08:18 UTC by Christopher Yeleighton
Modified: 2023-10-10 14:44 UTC (History)
3 users (show)

See Also:
Found By: Community User
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
chcao: needinfo? (giecrilj)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Yeleighton 2023-06-22 08:18:28 UTC
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.
Comment 1 Nikolai Nikolaevskii 2023-06-27 20:35:51 UTC
https://en.wikipedia.org/wiki/Signal_(IPC)#SIGILL
"Signal illegal"
The SIGILL signal is sent to a process when it attempts to execute an illegal, malformed, unknown, or privileged instruction.

https://de.wikipedia.org/wiki/SIGILL
https://ru.wikipedia.org/wiki/SIGILL
Comment 2 Chenzi Cao 2023-07-06 16:49:07 UTC
Hi Christopher, would you please help to provide the link of the documentation for Macro? Thanks!
Comment 3 Chenzi Cao 2023-10-10 14:44:00 UTC
Hi Christopher, I close this bug report now, please feel free to reopen it when you could provide required info and I would continue to find bugowner for it, thanks.