Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Different exceptions have different causes. Some exceptions are normal, and the exception only tells the kernel what it needs to do before allowing the software to continue running. Examples of this include a page fault telling the kernel it needs to load data from swap space, an undefined instruction exception telling the kernel it needs to emulate an instruction that the CPU doesn't support, or a debug/breakpoint exception telling the kernel it needs to notify a debugger. For these it's normal for the kernel to fix things up and silently continue.</p> <p>Some exceptions indicate abnormal conditions (e.g. that the software crashed). The only sane way of handling these types of exceptions is to stop running the software. You may save information (e.g. core dump) or display information (e.g. "blue screen of death") to help with debugging, but in the end the software stops (either the process is terminated, or the kernel goes into a "do nothing until user resets computer" state).</p> <p>Ignoring abnormal conditions just makes it harder for people to figure out what went wrong. For example, imagine instructions to go to the toilet:</p> <ul> <li>enter bathroom</li> <li>remove pants</li> <li>sit</li> <li>start generating output</li> </ul> <p>Now imagine that step 2 fails because you're wearing shorts (a "can't find pants" exception). Do you want to stop at that point (with a nice easy to understand error message or something), or ignore that step and attempt to figure out what went wrong later on, after all the useful diagnostic information has gone?</p>
    singulars
    1. This table or related slice is empty.
    1. POOS development: How to avoid an infinite loop after an exception routine
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBrendan
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POOS development: How to avoid an infinite loop after an exception routine
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI understand your point. I know it wouldn't make sense to continue executing a process which generated a segment fault, but I just *want* to do it, mainly out of curiosity. From what I've understood so far, it's not possible to do it in an easy way (no magic register defining the interrupt behaviour, for example).
      singulars
      1. PO
      1. USMr. Pixel
    2. COIf you actually do want to do it; then you have to implement a decoder to determine the length of the instruction from raw bytes in RAM. This would be a large amount of work for 80x86 (variable length instructions, prefixes, etc). Once you've got it "working" it still won't work in some cases. For example, imagine a page fault caused by "page not present" - you can't attempt to decode bytes that don't exist.
      singulars
      1. PO
      1. USBrendan
    3. COI know it would be a large amount of work. Haven't thought of the page faults, but that's not such a big issue (well at least, not yet, in my case).
      singulars
      1. PO
      1. USMr. Pixel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload