Intel Corporation (INTC) Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Intel Corporation (INTC)

INTC 36.15

-0.6%

Dec 24 12:59 PM EST

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Paul Engel who wrote (39555)	11/8/1997 1:36:00 AM
From: Buy Low Sell Hi	Read Replies (1) of 186894

Paul, I disagree again. It is certainly possible the processor can attempt to execute code (or data) from a "bogus" location if the stack is messed up. Two things will happen: 1) execution of unintended valid instructions or 2) an attempt to execute an invalid instruction. Valid instructions could potentially trash memory, write to I/O, etc., but the use of segment descriptor tables for each task can prevent that. Invalid instruction should generate a processor exception and be trapped by the OS. The whole point of a protected mode operating system is to prevent bad code in a user task from crashing the system. This bug circumvents that by locking up the processor from a user task. BLSH

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next