This redirect does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing: Software Low‑importance This redirect is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles Low This redirect has been rated as Low-importance on the project's importance scale. This redirect is supported by WikiProject Software (assessed as Mid-importance).

This is not correct (or at least partially incorrect). A trap is NOT a fault, and it does NOT occur following an error. It is part of the proper procedure to run any system call (such as, open/close/read/write file, ask for the time of day, etc.) It isn't surprising, since I'm not really sure how reliable "the jargon file" is... I'd suggest using any Operating System book/ University Course site and correct this (not so small) glitch. Like here: http://www.edugrid.ac.in/webfolder/OpSystems/2_IntroductionII/Book-G_Nutt/trap.html Thoughts?

Why do you assume that the jargon file is my source? Try

• IBM (March 1962). Reference Manual IBM 7090 Data Processing System (PDF). Fifth Edition. A22-6528-4. {{ cite book}}: Unknown parameter |separator= ignored ( help)
• IBM (1966). IBM 7094 Principles of Operation (PDF). A22-6703-4. {{ cite book}}: Unknown parameter |separator= ignored ( help)
• IBM (October 25, 1962). IBM 7094 Data Processing System Customer Engineering Instruction - Reference: supplement on trapping (PDF). S23-4002. {{ cite book}}: Unknown parameter |separator= ignored ( help)
• GE (July 1964). GE-635 Programming Reference Manual (PDF). CPB-1004. {{ cite book}}: Unknown parameter |separator= ignored ( help)
• GE (April 1968). GE-625/635 Programming Reference Manual (PDF). CPB-1004F. {{ cite book}}: Unknown parameter |separator= ignored ( help)

Shmuel (Seymour J.) Metz Username:Chatul ( talk) 18:46, 27 September 2010 (UTC) reply

The above references are woefully out of date. Try reading something that was published in, say, the last 40 years. — Preceding unsigned comment added by 38.69.12.5 ( talk) 03:42, 28 October 2013 (UTC) reply

The references may be old, but they are relevant to the historical meaning of the term. As to current usage, look at, e.g., z/Architecture Principles of Operation, SA22-7832-09. Shmuel (Seymour J.) Metz Username:Chatul ( talk) 20:39, 28 October 2013 (UTC) reply

This article should be tossed and completely rewritten. Aside from inaccuracies, it's a lousy example of English prose. — Preceding unsigned comment added by 38.69.12.5 ( talk) 03:40, 28 October 2013 (UTC) reply

I'm not sure how much belongs in the article, but Intel did not introduce the concept of an instruction intended for use by the software to cause a trap, although the detail of INT, of course, originated with Intel. Earlier examples are the Master Mode Entry (MME) instruction on the GE-600 series and the Supervisor Call instruction (SVC) on the IBM System/360.

Note that the call gate eliminates the need for INT. Shmuel (Seymour J.) Metz Username:Chatul ( talk) 20:02, 7 September 2018 (UTC) reply

I wrote a section Exception handling#Hardware exceptions which has most of the content of this page. I don't see anything important on here missing from that section - any objections to my redirecting this page to that section? -- Mathnerd314159 ( talk) 05:44, 12 January 2022 (UTC) reply

There is relevant information not present in either Trap (computing) or Exception handling#Hardware exceptions. Historically, trap has been used for several different types of interrupts

• All interrupts, including I/O
• All synchronous interrupts
• Interrupt caused by a trap instruction; There is a discussion at Talk:Illegal opcode#Split illegal and undefined that discusses some of the trap instructions.
  • Conditionally
  • Unconditionally

There is also the question of whether OS interface instructions like Master Mode Entry (MME), SVC and UUO should be considered as trap instructions. -- Shmuel (Seymour J.) Metz Username:Chatul ( talk) 15:24, 12 January 2022 (UTC) reply

So as I read that list, a trap is an interrupt, an interrupt, or an interrupt. Then I guess redirecting to interrupt would be more appropriate. Regarding the history and various usages etc., that can go in the interrupt article as a section. I don't think "trap" has enough usage in a computing context to merit its own article. -- Mathnerd314159 ( talk) 02:53, 19 January 2022 (UTC) reply

I would recommend merging Interrupt and Trap (computing), with {{ Main|Interrupt}} in Exception handling#Hardware exceptions. -- Shmuel (Seymour J.) Metz Username:Chatul ( talk) 15:13, 19 January 2022 (UTC) reply

OK, I moved everything into Interrupt, so now this page is a redirect. Good? -- Mathnerd314159 ( talk) 05:29, 21 January 2022 (UTC) reply

Looks good. It probably needs clarification of hardware context versus software context, with examples. I made one small change to note that what the OS resumes after an interrupt need not be the interrupted process. -- Shmuel (Seymour J.) Metz Username:Chatul ( talk) 14:25, 21 January 2022 (UTC) reply