View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000904 | LDMud 3.6 | Runtime | public | 2022-02-27 18:56 | 2022-09-19 22:45 |
| Reporter | paradox | Assigned To | Gnomi | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Platform | Linux | OS | NixOS | OS Version | 21.11 |
| Product Version | 3.6.5 | ||||
| Fixed in Version | 3.6.6 | ||||
| Summary | 0000904: LWO to LWO bad call_other causes SIGABRT | ||||
| Description | Using `efun::call_other` from an LWO, on an `ob` target that is itself an LWO, specifying a `fun` that does not exists causes LD to catch a SIGABRT from `interpret.c` failing an assertion: ``` ldmud: interpret.c:14379: eval_instruction: Assertion `sp[-1].type == T_ARG_FRAME' failed. Thread 1 "ldmud" received signal SIGABRT, Aborted. ``` | ||||
| Steps To Reproduce | I have a branch (https://github.com/ldmud/ldmud/compare/master...dune-mud:cpu-py-lwo-crasher?expand=1) that adds a very small unit test to `t-python` that reproduces the issue reliably. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-02-27 18:56 | paradox | New Issue | |
| 2022-02-27 22:05 | Gnomi | Assigned To | => Gnomi |
| 2022-02-27 22:05 | Gnomi | Status | new => assigned |
| 2022-09-19 22:45 | Gnomi | Status | assigned => resolved |
| 2022-09-19 22:45 | Gnomi | Resolution | open => fixed |
| 2022-09-19 22:45 | Gnomi | Fixed in Version | => 3.6.6 |
