View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000697 | LDMud | Runtime | public | 2009-11-01 03:18 | 2021-04-16 21:24 |
| Reporter | _xtian_ | Assigned To | zesstra | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | won't fix | ||
| Summary | 0000697: use 'culprit' in runtime_error() for simul-efun callers | ||||
| Description | The master-function runtime_error() has an argument 'culprit' that was added to get some information about the calling object in heart beats. It would be nice if we could use this parameter for other situations, too. Specifically, I would like to suggest this to get better information for errors in simul-efuns. This is a special case and often the error is not in the simul-efun itself, but in the previous_object() calling the simul-efun. But who that was will be lost, because while calling master::runtime_error() the caller-stack has already been emptied. So my suggestion is: Detect if an error is in the simul-efun-object and then add the calling-object as 'culprit' argument. Otherwise the mudlib has no way to get this data. | ||||
| Tags | No tags attached. | ||||
| External Data (URL) | |||||
| related to | 0000187 | new | New efun: raise_caller_error() |
|
|
What about debug_info(DINFO_TRACE, DIT_ERROR, ...)? We use this in the master in all calls to runtime error to store the stacktrace in an error storage for later reference. That includes the whole trace for the error, also during sefun calls. For some sefuns we also use set_this_object() before calling raise_error() in case of wrong arguments, which attributes the error to the right object. |
|
|
The stack trace for the error situation is available and with it all necessary information. Therefore we close this. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-11-01 03:18 | _xtian_ | New Issue | |
| 2009-11-01 09:32 | zesstra | Note Added: 0001577 | |
| 2009-11-01 10:10 | fufu | Relationship added | related to 0000187 |
| 2021-04-16 21:24 | zesstra | Assigned To | => zesstra |
| 2021-04-16 21:24 | zesstra | Status | new => closed |
| 2021-04-16 21:24 | zesstra | Resolution | open => won't fix |
| 2021-04-16 21:24 | zesstra | Note Added: 0002608 |
