| 18,11 → 18,11 |
|---|
| |
| /** |
| ------------ |
| CVS : $Id: signal.c,v 1.11 2004-06-16 08:12:32 giacomo Exp $ |
| CVS : $Id: signal.c,v 1.12 2005-01-08 14:46:18 pj Exp $ |
| |
| File: $File$ |
| Revision: $Revision: 1.11 $ |
| Last update: $Date: 2004-06-16 08:12:32 $ |
| Revision: $Revision: 1.12 $ |
| Last update: $Date: 2005-01-08 14:46:18 $ |
| ------------ |
| |
| This file contains: |
| 1294,7 → 1294,7 |
|---|
| kern_printf("\nSignal number %d...\n",sig); |
| if (act.sa_flags & SA_SIGINFO) |
| kern_printf("with value : %d\n",info->si_value.sival_int); |
| sys_abort(ASIG_DEFAULT_ACTION); |
| exit(ASIG_DEFAULT_ACTION); |
| } |
| |
| /* |
| 1355,10 → 1355,10 |
|---|
| /* (*) |
| when we are in an exception, we don't have to call the |
| really_deliver signal. |
| For example, when the capacity of a task is exausted, an event is |
| called. this event simply call scheduler, that call the task_epilogue. |
| For example, when the capacity of a task is exausted, an OSLib event is |
| called. this event simply call scheduler, that call the public_epilogue. |
| |
| the task_epilogue checks the capacity and raise an exception, BUT |
| the public_epilogue checks the capacity and raise an exception, BUT |
| we don't have to deliver this exception immediately. |
| |
| Why? because the task pointed by exec_shadow was extracted from the |